Update release

PATCH /api/v3/releases/{id}

Request

Response

URL

PATCH https://example.aha.io/api/v3/releases/123

JSON body

{
  "record": {}
}

cURL command

curl --request PATCH 'https://example.aha.io/api/v3/releases/123' \
  --header 'Authorization: Bearer YOUR_API_TOKEN' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data-raw '{
  "record": {}
}'

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 release

Request fields

Send only the fields you want to change inside a JSON record object. This applies to both PUT and PATCH.

Only writable fields for this endpoint are listed. Required flags reflect the endpoint schema; record and workspace validation also applies.

Search request fields

Field	Type	Response field
Name of the record.	string	`name`
Include name in request Accepted value shape and constraints Type: `string`
Start date of the record.	date	`start_date`
Include start_date in request Accepted value shape and constraints Type: `string` (date)
End date of the record.	date	`end_date`
Include end_date in request Accepted value shape and constraints Type: `string` (date)
Release date of the release.	date	`release_date`
Include release_date in request Accepted value shape and constraints Type: `string` (date)
Date when the release was released.	date	`released_on`
Include released_on in request Accepted value shape and constraints Type: `string` (date)
Date when development of the release started.	date	`development_started_on`
Include development_started_on in request Accepted value shape and constraints Type: `string` (date)
External release date of the release.	date	`external_release_date`
Include external_release_date in request Accepted value shape and constraints Type: `string` (date)
Precision of the external release date.	string	`external_date_resolution`
Include external_date_resolution in request Accepted value shape and constraints Type: `string` Allowed values: "sync", "exact", "week", "month", "quarter", "half", "year" Allowed values: `syncexactweekmonthquarterhalfyear`
Whether the release is a parking lot.	boolean	`parking_lot`
Include parking_lot in request Accepted value shape and constraints Type: `boolean`
Position of the record relative to its siblings.	integer	`position`
Include position in request Accepted value shape and constraints Type: `integer`
How progress is calculated for the release.	string	`progress_source`
Include progress_source in request Accepted value shape and constraints Type: `string` Allowed values: "manual", "from_features", "from_features_with_dependents", "from_release_phases", "from_release_phases_with_dependents", "from_todos", "from_todos_with_dependents", "from_remaining_estimate", "from_remaining_estimate_with_dependents", "from_features_completed", "from_features_completed_with_dependents", "from_epics", "from_epics_with_dependents", "from_sub_releases" Allowed values: `manualfrom_featuresfrom_features_with_dependentsfrom_release_phasesfrom_release_phases_with_dependentsfrom_todosfrom_todos_with_dependentsfrom_remaining_estimatefrom_remaining_estimate_with_dependentsfrom_features_completedfrom_features_completed_with_dependentsfrom_epicsfrom_epics_with_dependentsfrom_sub_releases`
How start and end dates are calculated for the release.	string	`duration_source`
Include duration_source in request Accepted value shape and constraints Type: `string` Allowed values: "manual", "from_release_phases_features", "from_sub_releases" Allowed values: `manualfrom_release_phases_featuresfrom_sub_releases`
Progress completed for the record.	number	`progress`
Include progress in request Accepted value shape and constraints Type: `number`
ID of the status assigned to the record.	string	`status`
Include status_id in request Accepted value shape and constraints Type: `string` Submit `status_id`; the response includes `status`.
ID of the owner associated with the release.	string	`owner`
Include owner_id in request Accepted value shape and constraints Type: `string` Submit `owner_id`; the response includes `owner`.
HTML description of the record.	string	`description`
Include description in request Accepted value shape and constraints Type: `string`
ID of the parent associated with the release.	string	`parent`
Include parent_id in request Accepted value shape and constraints Type: `string` Submit `parent_id`; the response includes `parent`.
Custom field values to set. Property names are custom field definition keys, and each value is one of the supported input formats below, depending on the field type. Attachment fields are read-only and can't be set.	object	`custom_fields`
Include custom_fields in request Accepted value shape and constraints Type: `object` Custom property values Type: `one of the shapes below` Supported shape 1 Text field Type: `string` Supported shape 2 Note field Type: `string` Supported shape 3 URL field Type: `string` (uri) Supported shape 4 Number field Type: `string` Supported shape 5 Date field Type: `string` (date) Supported shape 6 Checkbox field Type: `boolean` Supported shape 7 Single select field Type: `object` Minimum properties: 1 id Type: `string` name Type: `string` Supported shape 8 Conditional choice field Type: `object` Required properties: id. id Type: `string` Supported shape 9 Multi-select field Type: `array` Array item shape Type: `object` id Type: `string` name Type: `string` _destroy Type: `boolean` Supported shape 10 Records field Type: `array` Array item shape Type: `object` id Type: `string` _destroy Type: `boolean` Supported shape 11 Single custom table link Type: `object` Required properties: id. id Type: `string` Supported shape 12 Custom table links Type: `array` Array item shape Type: `object` id Type: `string` _destroy Type: `boolean` Supported shape 13 Worksheet field Type: `array` Array item shape Type: `object` Required properties: id, value. id Type: `string` value Type: `string or number or boolean or null` Supported shape 14 Scorecard field Type: `object` Minimum properties: 1 score Type: `number or null` score_facts Type: `array` Array item shape Type: `object` scoring_system_metric_id Type: `string` value Type: `number` _destroy Type: `boolean` Supported shape 15 Clear value Type: `null` Use your account’s custom field API keys and values matching each field’s type.
Users watching the record for update notifications. Items are merged into the existing collection: each item adds a record, or removes it with `_destroy: true`. Records not listed are left unchanged, and an empty array changes nothing.	array	`watchers`
Include watchers in request Accepted value shape and constraints Type: `array` Array item shape Type: `object` id Type: `string` _destroy Type: `boolean`

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
Type of the release.	string	No
Include type in response Allowed values: `releaserollup_release`
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
Release date of the release.	date	No
Include release_date in response
Date when the release was released.	date	No
Include released_on in response
Date when development of the release started.	date	No
Include development_started_on in response
External release date of the release.	date	No
Include external_release_date in response
Precision of the external release date.	string	No
Include external_date_resolution in response Allowed values: `syncexactweekmonthquarterhalfyear`
Whether the release is a parking lot.	boolean	No
Include parking_lot in response
Position of the record relative to its siblings.	integer	No
Include position in response
How progress is calculated for the release.	string	No
Include progress_source in response Allowed values: `manualfrom_featuresfrom_features_with_dependentsfrom_release_phasesfrom_release_phases_with_dependentsfrom_todosfrom_todos_with_dependentsfrom_remaining_estimatefrom_remaining_estimate_with_dependentsfrom_features_completedfrom_features_completed_with_dependentsfrom_epicsfrom_epics_with_dependentsfrom_sub_releases`
How start and end dates are calculated for the release.	string	No
Include duration_source in response Allowed values: `manualfrom_release_phases_featuresfrom_sub_releases`
Progress completed for the record.	number	No
Include progress in response
Status assigned to the record.	Status	No
Include status in response Expand this association to browse its response fields.
Owner associated with the release.	User	No
Include owner 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.
Workspace that contains the record.	Project	No
Include project in response Expand this association to browse its response fields.
Parent associated with the release.	Release	No
Include parent in response Expand this association to browse its response fields.
Features associated with the release. Omitted by default. Request the field for inline records with default sub-fields, or choose sub-fields (e.g., ?fields=features[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 features in response Expand this association to browse its response fields.
Release phases associated with the release. Omitted by default. Request the field for inline records with default sub-fields, or choose sub-fields (e.g., ?fields=release_phases[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 release_phases in response Expand this association to browse its response fields.
Children associated with the release. Omitted by default. Request the field for inline records with default sub-fields, or choose sub-fields (e.g., ?fields=children[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 children 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`.
Users watching the record for update notifications. Omitted by default. Request the field for inline records with default sub-fields, or choose sub-fields (e.g., ?fields=watchers[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 watchers in response Expand this association to browse its response fields.

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

Create and update responses also include fields submitted in the record body. Submitted association IDs return their associated response fields.

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 400, 401, 403, 404, 409

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

Error shape for 422

Type: object

error

Type: object

Required properties: status, code, message, details, request_id.

status

Type: integer

Allowed values: 422

code

Type: string

Allowed values: "record.validation_failed", "record.cannot_delete"

message

Type: string

details

Type: array

Array item shape

Type: object

field

Type: string

message

Type: string

code

Type: string

request_id

Type: string

Response envelope and pagination

record: a single record. Fields are documented above.

Download the complete OpenAPI specification