Coming soon

Check here to see what’s in the pipeline for Akoya!

Akoya API v2 updates

Please note that additions and new endpoints listed below may change in order of release or minor version number. Check back for updates!

v2.1 (live)

Addition of Statements product. This product includes two new endpoints which enable you to securely access your end-users' historical account statements. ​See the Statements guide.

v2.2 (live)

  • We’re adding an optional x-akoya-interaction-type header to all product endpoints to specify if a request is part of a batch process. While this header will remain optional in Akoya API v2, we highly recommend implementing it if a provider you’d like to subscribe to has indicated they will require this header from Akoya. See: Headers guide
  • To better organize product information, we’re reorganizing documentation to group product guides and endpoints. This will make it easier for you to understand how to use our products! To support this effort to clarify product usages, we’re updating tags in the Akoya API v2.2 OpenAPI specification.
  • The /account-info, /balances, and /accounts endpoints will have an additional 206 response to allow for partial responses.


New enrichment endpoint

  • Based on our /transactions endpoint, Akoya will offer a new endpoint which will take basic transaction data and enrich it with additional context and details. Expect to see more information when early access becomes available.


FDX 5.3 update.

  • Akoya will integrate additions to allow us to support FDX v5.3 including the new account category, commercialAccount.


New standardized data products.

  • Akoya will launch new endpoints designed to offer greater flexibility and even faster integration with standardized data. These new products will return network-wide, standardized Account Info, Balance, and Transaction data.

Consent flow updates

We’re making a change to how we authorize end-users and generate tokens by moving data recipients to a new token identity provider (IdP). The new IdP will improve Akoya’s network performance and will offer more flexibility with scoped client credentials and token life cycles.

Akoya will fully manage the migration of recipients from our existing IdP to the new one in a gradual, phased approach starting in our sandbox. See: Consent flow improvements.

A beta release is expected in our production environment in Q3 2023, but official timelines will be communicated in another announcement. This is still to be determined.

Management API

v1.2 (live)

With v1.2, the Management API will move from early preview to the stable version in our documentation and now includes a guide and a new endpoint to obtain service tokens.


We’re updating our Management API with the ability to add products to your current subscriptions. This new ability will be a breaking change and is a major version update.

Data Recipient Hub


This update of the Hub features support tickets, an in-app experience that allows users to contact Akoya or to file a production incident ticket. The first iteration of support tickets will allow you to create a ticket which is then assigned to an Akoya support specialist who will reach out via email to assist with your inquiry. Future enhancements to support tickets will allow the entire interaction to take place directly inside the Hub.

Account number tokenization

Akoya is launching the ability for data providers to use tokens instead of account numbers in financial data sharing. We announced this upcoming support in May 2022:

Akoya is the first third-party service provider to provide access to the Secure Token Exchange (STE), a new optional capability from The Clearing House (TCH) that issues tokens for financial institutions’ account numbers, for the RTP® network and EPN, the real-time payments and Automated Clearing House (ACH) networks operated by TCH. Akoya is the first third-party service provider for tokenized payments

What does this mean for data recipients?

This means your end-user’s account information is more secure. Real account numbers aren’t shared, but rather, you’ll use pointers to the account numbers. If you use the Akoya Payments product, you don’t have to do anything. The tokenized account numbers work the same as real account numbers.

For more information, see Reduce fraud risk with tokenized account numbers

And more

Expect more updates from Akoya! We’re working on additional features for the Data Recipient Hub and other new products.

More information coming soon!