APIs Integration

Current API reference

With the current structure, the API requests are sent to the respective recipient member directly. This requires each member to understand the metadata of the recipient member and use their base path while sending.

Existing approach to use the APIs by AA Ecosystem

Using Sahamati Router APIs

Sahamati Router makes it easy for the members to send the request to any recipient just by adding the recipient identifier in the header under x-recipient-id.

Using Sahamati Router APIs for AA Ecosystem
Particulars
Comments

Host

The base path to use by the members of Sahamati Router.

Headers

This will remain same as previous.

  • x-jws-signature - Authorization

  • Token (from sender)

Additional Headers

The recipient id is a required property. It is the identifier of the receiver to whom the API call needs to be forwarded.

x-request-meta

Was this helpful?