Akoya uses HTTP status and error codes to indicate the success or failure of a request. For status codes other than 200, the HTTP response body will contain an error entity.

HTTP Status CodesMeaning
100sInformational codes indicating that the request initiated by the browser is continuing.
200sSuccess codes returned when browser request was received, understood, and processed by the server.
300sRedirection codes returned when a new resource has been substituted for the requested resource.
400sClient error codes indicating that there was a problem with the request.
500sServer error codes indicating that the request was accepted, but that an error on the server prevented the fulfillment of the request.


FDX exception

Akoya error codes are consistent with FDX API 4.1 standards with the following exception:
The error code is returned as an integer rather than a string. See the example error body below.

Error body

  • code FDX error code as an integer
  • message Description of the error
   "message":"Invalid start or end date"
HTTP Status CodeFDX Error CodeError MessageDescription
400401Invalid inputInput sent by client does not satisfy API specification.
400702Invalid start or end dateStart or end date value is not in the ISO 8601 format.
400703Invalid date rangeThe start date is not earlier than the end date, or the date range is beyond what the system supports.
401602Customer not authorizedCustomer does not have authorization to perform this action. The customer may have revoked access through provider and would need to reauthenticate.
403403Subscription not foundThis error may be caused any of the following: 1. The providerId in your request is incorrect. 2. Your app isn’t subscribed to the requested provider. 3. Your app isn’t subscribed to the requested Akoya product. Please check the Akoya Hub to determine your subscription details.
404601Customer not foundCustomer with ID not found. Token may have been revoked.
404701Account not foundAccount with ID not found.
422704Account type not supportedRequest made for investment, loans, taxes, statements and other functions that we currently do not support. Error also covers certain account types that are not supported, such as if an account doesn’t support payment-networks.
500500Internal server errorCatch-all exception for requests that were not processed due to an Akoya-originated outage/issue.
500501Subsystem unavailableCatch-all exception for requests that were not processed due to a Data Provider-originated outage/issue.

Change log

2022-Oct-21Updated description for FDX 704/HTTP 422 error
2022‑Mar‑2Added error 704 to support payment-networks error
2023-Jan-8Added definition for error 403 - subscription not found