Service status ·A8 Core™ · The Operating System for Financial Accounts ·The account operating system · API-first
Support/Limits & status
Developer support

Limits & status

Rate limits, pagination, the error envelope, safe retries, and where to watch platform health. The operational details that keep an integration reliable at scale.

Rate limits

Limits are applied per key. When you exceed your allowance the API returns HTTP 429; back off and retry. Treat limits as a signal to batch and parallelize sensibly rather than a hard wall — talk to us if your volume is growing.

Spread bulk work over time and honor 429 with exponential backoff. Steady throughput beats bursts that trip the limiter.

Pagination

List operations accept PageNumber and PageSize and return a TotalCount alongside the records, so you can page deterministically.

List request
"PageNumber": 1,
"PageSize": 50

The error envelope

Handled application errors still return HTTP 200 with Status = 0 and a ResponseStatus object describing the failure. Transport, authentication, and signature failures return a non-2xx HTTP status.

Error envelope
"RequestId": 1736472902501,
"Status": 0,
"ResponseStatus": { "ErrorCode": "ClientNotFound", "Message": "No client matches the supplied ClientId." }
ClassHTTPRetry?
Validation / not found200 with Status: 0No — fix the request.
Auth / signature401No — re-sign correctly.
Rate limit429Yes — backoff.
Transient / server5xxYes — backoff with the same ProviderReferenceId.

Retrying safely

Because writes are idempotent on ProviderReferenceId, you can retry a timed-out or 5xx request without risk of double-applying it. Use exponential backoff with jitter, and always reuse the original reference on the retry.

Status and incidents

Live availability and incident history are published on the status page. Subscribe there to be notified of incidents and maintenance, and watch for account.updated webhooks to confirm processing resumed after any disruption.

Support and escalation

For integration help or to report a problem, email support@a8core.com with the RequestId from the affected response — it lets us trace the request end to end immediately.

Where to next

Need a hand?

Talk to a human.

Stuck on an integration? Our team answers developer questions directly.

Scroll to Top