Integration status

GET /api/v1/integration-status read:inventory

Open or acknowledged integration issues affecting your account, with SLA-breach flags. Issues are opened automatically when one of your writes (transfer, withdrawal, declared value, order) hits an unexpected server-side error — you don’t need to report those; they are already on our board when you see them here. Your agreement sets the response window; this endpoint is the source of truth for what’s open. If breached > 0, our response window has elapsed on something we owe you a reply on.

Try it GET /api/v1/integration-status
response

Not run yet. Press Run to make a live call against https://service.rip.fun (through this demo's server-side proxy; the API key never reaches the browser).

curl (tracks the inputs above)
curl -X GET 'https://service.rip.fun/api/v1/integration-status' \
  -H 'X-API-Key: rip_…'

Response fields (data)

FieldDescription
openCount of non-RESOLVED issues
breachedSubset whose sla_due_at is past now
issues[].id / issue_type / severity / statusIssue rows — severity defaults "error", status OPEN | ACKNOWLEDGED
issues[].opened_at / sla_due_at / sla_breachedWhen it opened + the response deadline (business days, warehouse local time)

Errors

StatusCodeWhen
403Tenant API key requiredkey is not tenant-scoped, or lacks read:inventory

See Errors for the response envelope and the full code list.