Update iteration

PATCH /api/v3/iterations/{id}

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

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

ID or reference number of the iteration

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.

FieldTypeResponse field

Name of the record.

stringname

Status of the iteration.

stringstatus

Start date of the record.

datestart_date

End date of the record.

dateend_date

Duration of the iteration.

integerduration

Goal of the iteration.

stringgoal

Progress completed for the record.

numberprogress

HTML description of the record.

stringdescription

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.

FieldTypeReturned by default

Unique record ID.

integerYes

URL to view the record in Aha!

stringYes

API URL for the record.

stringYes

Name of the record.

stringYes

Reference number of the record.

stringYes

Date and time when the record was created.

date-timeNo

Date and time when the record was last updated.

date-timeNo

Status of the iteration.

stringNo

Start date of the record.

dateNo

End date of the record.

dateNo

Duration of the iteration.

integerNo

Goal of the iteration.

stringNo

Progress completed for the record.

numberNo

HTML description of the record.

NoteNo

Workspace that contains the record.

ProjectNo

Features associated with the iteration. 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.

CollectionNo

Requirements associated with the record. Omitted by default. Request the field for inline records with default sub-fields, or choose sub-fields (e.g., ?fields=requirements[default]). Capped at 25 records. Only available on the top-level resource.

CollectionNo

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