Documentation / Guides
Polling and retries
Read the latest result without submitting or charging for another decision.
GET
/v1/decisions/{id}Shell · curl
curl -i "$ARBIRO_BASE_URL/v1/decisions/$DECISION_ID" \
-H "Authorization: Bearer $ARBIRO_API_KEY"Submission versus current state
| 200 completed | Read answers and save decision_id. |
|---|---|
| 202 running | A concurrent submission is in progress. Respect Retry-After: 1 and poll Location. |
| 202 review_pending | A person must resolve the review. Keep the review_task_id and poll Location. No final answer exists yet. |
A repeated POST returns the original committed submission, even if it handed off to review. GET returns the latest projection, including a completed human resolution. Other tenants’ IDs are not visible.
Handle failures
| 400 / 415 | Check the question definition, JSON and Content-Type: application/json. |
|---|---|
| 401 / 403 / 404 | Check credentials, scope, and tenant ownership. An inference key cannot change billing or edit policies. |
| 402 | Insufficient funds for a new hold. A request denied before the first dispatch may resume with its original key after funding. |
| 409 / 412 / 428 | A retry key conflicts with the input, an edit revision is stale, or a required revision header is missing. |
| 429 | Back off on rate/concurrency limits and respect Retry-After. A retained-claim quota is different: consult your administrator. |
| 503 indeterminate | A provider may already have received the request. Preserve the ID and reconcile; do not create a new retry key to force dispatch. |
Vendor error bodies differ: TypeSafe uses detail; OpenAI uses an error object.