Request an immediate scheduler pass
POST
/v1/batch-jobs/processNormally unnecessary because every deployment starts an embedded durable Batch worker.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
None.
Query parameters
None.
Body schema
This endpoint does not require a request body.
None.
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200No work was claimableapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| claimed | integer | Yes | — |
| reconciled | object | Yes | — |
| reconciled.succeeded | integer | Yes | — |
| reconciled.failed | integer | Yes | — |
| recoveredLeases | integer | Yes | — |
202One or more jobs were claimedapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| claimed | integer | Yes | — |
| reconciled | object | Yes | — |
| reconciled.succeeded | integer | Yes | — |
| reconciled.failed | integer | Yes | — |
| recoveredLeases | integer | Yes | — |
Request an immediate scheduler pass
Loading...
Response 200
Loading...