Endpoint
Purpose
Queues human input for a case that is currently paused inINPUT_NEEDED.
Authentication
Path Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
id | string | Yes | Case ID |
Request Body
| Field | Type | Required | Notes |
|---|---|---|---|
inputRequestId | string | Yes | Must match the active request on the case |
providedContext | string | Yes | Your answer or missing context |
Example Request
Successful Response
What 202 Accepted Means
202 means:
- the input passed validation
- the case was found and owned by the caller
- the internal queue accepted the follow-up work
- the worker already processed your answer
- the case has already left
INPUT_NEEDED - a reply was already sent
Transient State To Expect
Immediately after202:
- the API updates
inputRequestStatustoRESOLVED - the case can still be
INPUT_NEEDEDuntil the worker finishes
Conflict Errors
This endpoint returns409 when:
- the case is not currently waiting for input
- the active request is no longer pending
- the
inputRequestIddoes not match the currently active request
Errors
| Status | Code | Meaning |
|---|---|---|
400 | INVALID_REQUEST | Missing case ID, malformed JSON, or invalid body |
401 | UNAUTHORIZED | Missing or invalid API key |
403 | FORBIDDEN | Inactive API key or case belongs to another user |
404 | CASE_NOT_FOUND | No case exists for that ID |
409 | CASE_NOT_WAITING_FOR_INPUT | Case is not paused for input |
409 | INPUT_REQUEST_NOT_PENDING | Input request is already resolved |
409 | INPUT_REQUEST_MISMATCH | Input request ID is stale or wrong |
500 | INTERNAL_ERROR | Queueing the input failed |