Akahu is announcing the release of a new (beta) endpoint:
/parties 🥳. This endpoint provides identity data relating to the parties that are registered at the institutions that your users connect to your application.
Today Akahu is releasing brand new beta endpoints: The
BNZ recently made a change that would require Akahu to provide BNZ account connectivity via “screen scraping”.
Today we are introducing our JS SDK, which makes interacting with the Akahu API simple and straightforward.
_user field on webhook events was intended to make it easier to match up which events were sent to which of the recipient's users. In hindsight, this is not terribly useful, and duplicates what the
state parameter is supposed to be doing.
profile field on connections was intended to allow a banner image to go with a connection logo.
We say an account has been "refreshed" when we have just gone to the bank and retrieved the latest balance, metadata and transactions.
Beginning on Monday the 31st of May 2021, the
/me endpoint will now return two new fields:
Beginning on the 1st of January 2021, Akahu will require all API requests to
api.akahu.io that are authorised with a User Token to include a new header,
X-Akahu-ID with the value of your App Token.