Desk

Send Desk Reply

SENDS AN EMAIL to a real person, then resolves the card.

Not idempotent, and it cannot be: the inbox send path carries no request id and no dedupe key. What protects a caller instead is the CARD: it is claimed before the send, guarded on still being pending, so only one request can win and a second gets a 409 having sent nothing.

A retry after a timeout is therefore safe in the usual case and silent in one: a crash between the claim and the send leaves a resolved card whose mail never went. That is deliberate - recoverable by a human, unlike a duplicate email, which cannot be recalled.

The opt-out check runs AGAIN here. reply-target already asked, but that answer is as old as the caller's editing session and a STOP that arrived meanwhile must not be sent through.

post/desk/decisions/{decision_id}/send-reply

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/desk/decisions/{decision_id}/send-reply
  • Auth: HTTP bearer

Path parameters

decision_idstring required

Decision id (UUID).

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

subjectstring nullable
bodystring required

The reply body. Reaches a real person.

Response

Successful Response

dataDeskPayload required

An open envelope for one desk object.

Open on purpose - see the module docstring. A rebuilder gets every field the desk returns, including ones added after this contract version.

Changes

No recorded changes to this operation across all 2 revisions of this API.