Get requirement

GET /api/v3/requirements/{id}

Request

Response

URL

GET https://example.aha.io/api/v3/requirements/123

cURL command

curl --request GET 'https://example.aha.io/api/v3/requirements/123' \
  --header 'Authorization: Bearer YOUR_API_TOKEN' \
  --header 'Accept: application/json'

Request conventions

API key or OAuth2 access token. See Authentication.

Use your account domain and token in copied requests. Request values and conditional fields must satisfy your account’s validation rules.

URL settings

Account subdomain

The part before .aha.io. Leave blank to use the example domain.

ID or reference number of the requirement

Response fields

Choose which fields to include in the response. Expand a field for examples and associated fields. Collections can only be returned on the top-level resource, not inside an associated resource.

Default response fields are returned until you select specific fields.

Search fields

Field	Type	Returned by default
Unique record ID.	integer	Yes
Include id in response
URL to view the record in Aha!	string	Yes
Include html_url in response
API URL for the record.	string	Yes
Include url in response
Name of the record.	string	Yes
Include name in response
Reference number of the record.	string	Yes
Include reference_num in response
Date and time when the record was created.	date-time	No
Include created_at in response
Date and time when the record was last updated.	date-time	No
Include updated_at in response
Start date of the record.	date	No
Include start_date in response
End date of the record.	date	No
Include end_date in response
Position of the record relative to its siblings.	integer	No
Include position in response
Initial work estimate for the record.	number	No
Include initial_estimate in response
Detailed work estimate for the record.	number	No
Include detailed_estimate in response
Remaining work estimate for the record.	number	No
Include remaining_estimate in response
Work completed for the record.	number	No
Include work_done in response
Status assigned to the record.	Status	No
Include status in response Expand this association to browse its response fields.
User assigned to the record.	AssignedToUser	No
Include assigned_to_user in response Expand this association to browse its response fields.
HTML description of the record.	Note	No
Include description in response Expand this association to browse its response fields.
Feature associated with the requirement.	Feature	No
Include feature in response Expand this association to browse its response fields.
Iteration associated with the record.	Iteration	No
Include iteration in response Expand this association to browse its response fields.
User who created the record.	User	No
Include created_by_user in response Expand this association to browse its response fields.
Team assigned to the record. Availability depends on account settings.	Project	No
Include team in response Expand this association to browse its response fields.
Team status assigned to the record. Availability depends on account settings.	Status	No
Include team_status in response Expand this association to browse its response fields.
Program increment associated with the record.	ProgramIncrement	No
Include program_increment in response Expand this association to browse its response fields.
Time code assigned to the record. Only available when timesheets are enabled for the account. Availability depends on account settings.	TimeCode	No
Include time_code in response Expand this association to browse its response fields.
Tags associated with the requirement. Omitted by default. Request the field for inline records with default sub-fields, or choose sub-fields (e.g., ?fields=tags[default]). Capped at 25 records. Only available on the top-level resource.	Collection	No
Collection envelope Records use the associated fields below. Type: `object` Required properties: records, has_more. url Type: `string` (uri) has_more Type: `boolean` next_url Type: `string` (uri) Include tags in response Expand this association to browse its response fields.
Custom field values. Property names are custom field definition keys, and each value is one of the supported formats below, depending on the field type. Omitted unless requested with the fields parameter or submitted in the request. Fields with no stored value are omitted.	object	No
Include custom_fields in responseCustom field API key Custom field keys depend on your account. Request `fields=custom_fields` or `fields=custom_fields.your_key`.

Search matches the start of a field path and includes matching associations’ subfields. Use a dotted path to search within a specific association.

Response field selection

Return selected fields with a comma-separated fields parameter, or add a field to the defaults with fields=default,{field}. Expand an association above for its supported subfields and selection examples.

See field selection for details.

Response statuses

Error shape for 401, 403, 404

Type: object

error

Type: object

Required properties: status, code, message, request_id.

status

Type: integer

code

Type: string

message

Type: string

request_id

Type: string

Response envelope and pagination

record: a single record. Fields are documented above.

Download the complete OpenAPI specification