agency-board

POST /v1/agency/client/boards/{boardId}/requests

Raise a request with the agency.

All agency-board endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The endpoint checks agency.board.client_view; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/agency/client/boards/{boardId}/requests \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "title": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

⚖️ Owner ruling 2026-08-31 — a client may raise a card, in the board's single intake column and nowhere else. The request body carries a title and a body and nothing that could steer it elsewhere: the column and the visibility are set by the engine, not accepted and overridden, because a field accepted and overridden is a field somebody later stops overriding.

Parameters

NameTypeRequiredWhat it is
boardId (path)UuidYesProject board ID (UUIDv7).

Request body

NameTypeRequiredWhat it is
titlestringYes—
bodystringNo—

Response

NameTypeRequiredWhat it is
idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
column_idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
titlestringYes—
bodystringNo—
due_atstringNo—
raised_by_usbooleanNoWhether the client raised this card. Named from the READER's side, because this payload is only ever read by the client.
created_atstringNo—
updated_atstringNo—

Errors this endpoint can return

401 · 403 · 404 · 422