Dependency readiness check
GET
/v1/readyVerify that the API can acquire and query its configured data store. Kept separate from process liveness so dependency incidents do not cause restart loops.
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.
200API dependencies are readyapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| status | ready | Yes | Current lifecycle status. |
| database | string | Yes | — |
| latencyMs | integer | Yes | — |
| timestamp | string | Yes | — |
503A required dependency is unavailable
None.