Vendor-reported · Accounting API

Downstream API status

Is it you, Apideck, or the vendor? What the vendors behind each connector report on their own status pages, next to Apideck’s own platform status, so you can tell which side an error is on before you change any code.

Apideck platform · Operational

  • Unify API
  • Vault API
  • Proxy API
  • Webhooks
  • Connector API

status.apideck.com · Reported Oct 21, 15:19 UTC · refreshes every 5 min

Could not reach status.sage.com, status.exact.com, status.freshbooks.com, status.fortnox.se, status.visma.com, status.simployer.com, status.factorialhr.com, status.fourth.com, status.homerun.co, status.jumpcloud.com, status.justworks.com, status.namely.com, status.payroll.nmbrs.com, status.activecampaign.com, status.teamleader.eu, status.lightspeedhq.com, jira-service-management.status.atlassian.com, status.shortcut.com on the last refresh. Connectors on those vendors show as “Feed unavailable” until the next one.

Vendors reporting an incident right now

Based on each vendor’s public status page. We relay what they publish and do not measure it ourselves, so an incident can be under way before it appears here.

9 of 14 vendors with a public status feed report all API components operational.

No vendor with a public status feed is reporting an incident on an API component. If you are seeing errors, check your request logs for the downstream response first.

Last 90 days, per connector

22 with a status feed · 27 without

  1. Exact OnlineExact
    Feed unavailable
    0 / 0↗
  2. Exact Online NLExact
    Feed unavailable
    0 / 0↗
  3. Exact Online UKExact
    Feed unavailable
    0 / 0↗
  4. FortnoxFortnox
    Feed unavailable
    0 / 0↗
  5. FreshBooksFreshBooks
    Feed unavailable
    0 / 0↗
  6. Sage IntacctSage
    Feed unavailable
    0 / 0↗
  7. Sage Intacct RESTSage
    Feed unavailable
    0 / 0↗
  8. SpirisVisma
    Feed unavailable
    0 / 0↗
  9. Visma eAccountingVisma
    Feed unavailable
    0 / 0↗
  10. Visma NetvisorVisma
    Feed unavailable
    0 / 0↗
  11. FreeAgentFreeAgent
    Operational
    90 days ago100% of days without an API incidentToday
    0 / 0↗
  12. Intuit Bank FeedsIntuit Developer
    Operational
    90 days ago98.9% of days without an API incidentToday
    1 / 5↗
    1 incident, 5 advisories on 2 status-page components
  13. Intuit Enterprise SuiteIntuit Developer
    Operational
    90 days ago98.9% of days without an API incidentToday
    1 / 5↗
    1 incident, 5 advisories on 2 status-page components
  14. NetSuiteOracle NetSuite
    Operational
    90 days ago100% of days without an API incidentToday
    0 / 0↗
  15. PennylanePennylane
    Operational
    90 days ago100% of days without an API incidentToday
    0 / 0↗
  16. QuickBooksIntuit Developer
    Operational
    90 days ago98.9% of days without an API incidentToday
    1 / 5↗
    1 incident, 5 advisories on 3 status-page components
  17. Restaurant365Restaurant365
    Operational
    90 days ago100% of days without an API incidentToday
    0 / 1↗
    0 incidents, 1 advisory on 2 status-page components
  18. RilletRillet
    Operational
    90 days ago100% of days without an API incidentToday
    0 / 1↗
    0 incidents, 1 advisory on 2 status-page components
  19. StripeStripe
    Operational
    90 days ago98.9% of days without an API incidentToday
    1 / 12↗
    1 incident, 12 advisories on 2 status-page components
  20. WaveWave
    Operational
    90 days ago98.9% of days without an API incidentToday
    1 / 3↗
    1 incident, 3 advisories on 3 status-page components
  21. XeroXero
    Operational
    90 days ago97.8% of days without an API incidentToday
    2 / 7↗
    2 incidents, 7 advisories on 8 status-page components
TimelineOutage reportedIncident reportedAdvisoryMaintenanceNo incidentNot published

Status page we cannot read yet

These vendors publish a status page, but not in a form we can read automatically. Follow the vendor page directly for now.

No public status page

These vendors do not publish a status page we could find. Downstream errors from them show up only in your request logs and in Unify’s error responses.