Version
POST

Add a design reference

/v1/projects/{project}/design-references in the Design References API.

curl -X POST https://api.example.test/v1/projects/$PROJECT_ID/design-references \  -H "Authorization: Bearer $TOKEN" \  -H "Idempotency-Key: $(uuidgen)" \  -H "Content-Type: application/json" \  -d '{        "title": "Checkout flow",        "url": "https://www.figma.com/file/aB3dE5fG7hJ9kL1mN3pQ5r/Checkout",        "kind": "figma",        "referenceable_type": "component",        "referenceable_id": "c2d3e4f5-a6b7-4c8d-9e0f-1a2b3c4d5e6f",        "version": "v3"      }'

title and url are required; the address must be http or https. kind defaults to other. The reference hangs off the whole project unless referenceable_type is component and referenceable_id names one of the project's components. The token holder is remembered as added_by.

Answers 201 with the reference and emits design_reference.created.

POST
/v1/projects/{project}/design-references

Requires ability

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

Delivered to every endpoint subscribed to it once the change is made.

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

Idempotent

Send the header on every call; the same key replays the original response for 24 hours.

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

project*string

The project, bound by the middleware.

Formatuuid

Header Parameters

Idempotency-Key*string

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Formatuuid

Request body

JSONWhat the request carries

A design reference to add or change. Only title and url are required on a create; the kind defaults to other and the reference hangs off the whole project unless a component is named. On an update, a field left out keeps its value and a field sent as null is cleared.

Responses

201Created

The reference, 201.

400Bad request

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

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. On this endpoint: FORBIDDEN: when the token holder's role on the project does not carry design-reference:create.

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. On this endpoint: RESOURCE_NOT_FOUND: when referenceable_id is not a component of the project.

409Conflict

The key was already used in the last 24 hours with a different request body.

422Validation failed

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a role code already taken or a team the caller does not own, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when a field is malformed, when the address is not an http or https link, or when referenceable_type is component and referenceable_id is missing.

425Too early

The first request with this key is still running; retry in a few seconds and the original response is replayed.

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