Version
GET

Get a change request

/v1/change-requests/{changeRequest} in the Change Requests API.

curl https://api.example.test/v1/change-requests/$CHANGE_REQUEST_ID \  -H "Authorization: Bearer $TOKEN"

One change request with the records it touches. A request of a project the token may not see, or one a client guest neither raised nor asked for, is 404 RESOURCE_NOT_FOUND.

  • reason is new_requirement, clarification, defect, regulatory, client_request, technical_debt or scope_reduction; status is submitted, under_analysis, awaiting_approval, approved, rejected, implementing, implemented, verified or closed; impact_level is low, medium or high; priority is lowest, low, medium, high or highest.
GET
/v1/change-requests/{changeRequest}

Requires ability

The token must hold this ability, or the call is refused with 403.

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken
AuthorizationBearer <token>

A personal access token minted in the app under Account Settings, then API Tokens, sent as Authorization: Bearer zg_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team, and optionally to one project, at mint time.

In: header

Path Parameters

changeRequest*string

The request, bound by the middleware.

Formatuuid

Responses

200OK

The request with the records it touches.

401Unauthorized

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (a zg_test_ token on production).

403Forbidden

The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who registered a row answers FORBIDDEN with the same status, and says so in its own description.

404Not found

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

429Too many requests

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

How is this guide?

Last updated on