agency-board

POST `/v1/agency/boards/{boardId}/questions/{questionId}`

Record an answer the agency was given another way.

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

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/boards/{boardId}/questions/{questionId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "body": <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

For an answer that arrived by phone or email. The client's own answer route is `POST /v1/agency/client/boards/{boardId}/questions/{questionId}/answer`.

Parameters

Name	Type	Required	What it is
`boardId (path)`	`Uuid`	Yes	Project board ID (UUIDv7).
`questionId (path)`	`Uuid`	Yes	Board question ID (UUIDv7).

Request body

Name	Type	Required	What it is
`body`	`string`	Yes	—

Response

Name	Type	Required	What it is
`id`	`Uuid`	Yes	UUIDv7 identifier — sortable by creation time (docs/02 §8).
`card_id`	`Uuid`	Yes	UUIDv7 identifier — sortable by creation time (docs/02 §8).
`body`	`string`	Yes	—
`status`	`string<open, answered, cancelled>`	Yes	—
`answer_body`	`string`	No	—
`answered_at`	`string`	No	—
`created_at`	`string`	Yes	—
`asked_by`	`AgencyBoardActor`	No	—
`answered_by`	`AgencyBoardActor`	No	—

Errors this endpoint can return

401 · 403 · 404 · 422

POST /v1/agency/boards/{boardId}/questions/{questionId}