Accounts / API reference
Health check
Request and response reference for GET /v1/health.
GET
/v1/healthAuthentication: API key
Use the base URL and access configuration provided to your institution. Examples are request templates, not transaction results. Field tables focus on client fields; preserve additional metadata returned by the configured service.
Request
Keep API keys in your backend. Required entitlements and institution scope still apply.
curl -X GET "$OSAI_API_BASE_URL/v1/health" \
-H "Authorization: ApiKey $OSAI_PUBLIC_ID:$OSAI_API_SECRET"Parameters
No endpoint-specific path or query parameters are defined. Authentication and access policy still apply.
Request body
This operation does not define a JSON request body.
Responses
Inspect HTTP status before parsing a body. These tables describe client response fields rather than invented successful transaction payloads.
200 · Service healthy
| Field | Type | Description & constraints |
|---|---|---|
statusRequired in parent object | string | Defined by the resource contract. |
request_idRequired in parent object | string | Defined by the resource contract. |
Retries & recovery
Keep the original request identifiers and any required idempotency key. A timeout does not establish failure. Read the original resource or command before another financial write; use expected versions for concurrent changes.