# 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.	https://api.sandbox.sahamati.org.in/proxy
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

Particulars

Comments

Host

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

https://api.sandbox.sahamati.org.in/proxy

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

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://developer.sahamati.org.in/no-longer-relevent/technical-specifications/router-api-specs/apis-integration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.