Skip to main content

Approve / Reject Result

Approve or reject a structuring result. POST /approve approves the result; POST /reject rejects it. Both return the updated status.

Submit an approval or rejection decision for a structuring result that is pending manual review. Approving a result triggers the gate's on_approve action (typically delivery). Rejecting it removes the result from the approval queue without triggering delivery. Both actions require the gate_id to record which gate the decision applies to.

The gate_id parameter is required. Each decision is recorded against a specific gate, allowing multiple gates to independently control the same result.
POST/v1/structuring/approvals/{id}/approve

Response

Response fields

idstringApproval decision UUID.
dataspace_result_idstringUUID of the structuring result.
statusstringDecision status: approved or rejected.

Response

{
  "id": "e5f6a7b8-c9d0-1234-efab-345678901234",
  "dataspace_result_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "status": "approved"
}

Errors

Error responses

400bad_requestgate_id is required.
401unauthorizedMissing or invalid API key.
404not_foundStructuring result or approval gate not found, or they do not belong to your organization.
429rate_limitedToo many requests. Retry after the period indicated in the Retry-After header.

After approving, the gate's on_approve action fires -- typically emitting a delivery signal. To batch-approve an entire run's results at once, iterate the pending approvals from GET /v1/structuring/approvals/pending, approve each individually, then call POST /v1/structuring/delivery/{runId} to trigger delivery for the full run.