Is it Apideck or the provider? Checking status during an outage
When calls start failing, the problem can be on Apideck's side or at the provider (QuickBooks, Xero, NetSuite and so on). Two status pages and your logs tell you which.
1. Check Apideck's status page
status.apideck.com shows the status of the Apideck platform: the Unify API, Proxy API, Vault, File Storage, Webhooks, Logs and the Connector API, plus the dashboard and docs. Incidents and their updates are posted there.
You can subscribe by email, Slack or RSS, so you hear about incidents without checking.
2. Check the provider's status
developers.apideck.com/status/connectors collects what the providers behind our connectors report on their own status pages, grouped by Unified API. It shows current incidents and a 90-day history per connector.
It shows what each provider reports. Apideck doesn't measure it, and providers don't always report every problem.
Not every provider publishes a status page we can read. Those are listed as such.
You can subscribe with RSS, for everything or one connector, for example
developers.apideck.com/api/downstream-status-feed?connector=quickbooks.
3. Look at the error and the logs
The error response tells you where it came from:
Error | Where the problem is | What to do |
|---|---|---|
| The provider returned an error. Its status code is in | Check the provider's status. Retry 5xx errors later. |
| The provider's rate limit | Retry with backoff. See rate limits. |
| The connection's credentials were rejected | Your customer reconnects in Vault. See Why did my connection stop working? |
| Apideck | Check status.apideck.com, then contact support. |
In the dashboard Logs, open the failed request and its downstream (child) request to see exactly what the provider answered. See investigating a failed request.
During a provider outage
Retry reads later with backoff. Temporary provider errors don't disconnect your customer's connection, so they don't need to reconnect.
Be careful retrying creates. A create that timed out may still have gone through. See A create request timed out: how to retry without creating duplicates.
Webhooks catch up. Virtual webhooks pick up changes on the next successful sync.
Contact Apideck support through the Customer Portal (the Requests link at the top of this help center), your Slack channel with us, or support@apideck.com. Include the time of the failing request, the consumer ID and the connector. For Proxy API calls, also include the x-apideck-request-id response header.