v2.2.1 plus network enhancements! (November 16, 2023)

Akoya has made improvements to our v2.2 specification, added a new error, and enhanced network protections to prevent DDoS (distributed denial-of-service) attacks and manage unusual, high call volumes.

Read on for more details on how to take advantage of our new error code and the OpenAPI update to Akoya v2.2.1.

Network protections

Akoya has made enhancements to network protections as a precaution against unusual network traffic. We do not anticipate that the improvements will impact current recipient apps on our network. These changes could be seen in the following ways:

  • Sandbox now has a limit of 5 TPS (transactions per second).
  • A new error code for "too many requests" has been added.

New error code

A new error will be returned in the cases of unusual network traffic.

HTTP status: 429

  "message":"Too many requests"

Will this impact my app?

Based on Akoya analysis, there should no impact to recipients currently on the network. We do not anticipate that your app will receive this error.

What does this mean for you?

Akoya continues to refine error messaging. While adding error codes are non-breaking changes, we recommend that you update apps to handle new error codes to refine your app’s integration and provide improved experiences for end-users.

If your app does receive this error, we recommend sending bulk requests at a slower rate.

This should be considered along with the addition of the x-akoya-interaction-type to indicate if a request is part of a batch process or a real-time, end-user interaction so that your app can manage the speed and number of calls when making bulk data calls. See: Headers.

Akoya v2.2.1 update

The OpenAPI specification update includes a few improvements:

  • v2.2.1
    • Fixed typo in accountIds query parameter for /accounts-info, /balances, /accounts
    • Added security method for Account holder information to bear token. Missing method defaulted to basic auth.
    • Added examples and descriptions to some schemas
    • Added HTTP status 429 FDX error 1207 to all endpoints
      • Also added error codes previously documented but not included as endpoint responses in the specification, such as 400, 401, 404, 500, 501, 503.

For more information, please reference updated documentation: