SahamatiNet
latest
latestv1.0
latest
latestv1.0
  • Background
  • SahamatiNet POC
    • Applications
    • Observability
    • Integration Steps
      • Sandbox Onboarding
      • IAM APIs
      • CR APIs
      • Integration with Router
        • Sample Code Snippets
          • Python
          • Java
          • JavaScript
          • GoLang
          • C#
        • Router APIs Specifications
          • FIU API Specification
          • AA API Specification
          • FIP API Specification
      • ReBIT Workflows using Router
        • Account Discovery & Linking
        • Consent Workflow
        • FI Request Workflow
    • Integration with Simulators
      • AA Simulator
      • FIP Simulator
      • FIU Simulator
    • Validation of Integration
  • Release Calendar
    • Deprecation of V1 API Endpoint URLs
    • Client Secret Rotation
    • Deactivation of Deprecated V1 APIs
  • Glossary
  • Guidelines
  • Frequently Asked Questions
  • How To Guides
    • How To Onboard to Sandbox ?
    • How To Decide on an Entity ID ?
    • How To Generate a Certificate ?
    • How To Generate Tokens ?
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. No Longer Relevent
  2. Technical Specifications

Router API Specs

Was this helpful?

Integration Steps

Outlined below are the changes that members need to make to their implementation to use the Sahamati Router.

  • Using Sahamati Router API endpoint as base path for all the requests.

  • Add the recipient ID under the new header x-request-meta with recipient-id in a JSON object which is the identifier of the receiver to whom the API call needs to be forwarded.

    • The value of the x-request-meta is Base64 string of the JSON object with recipient-id.

    • This strucutre helps us to easily extend the JSON object by adding the required attributes for future use cases.

x-request-meta: <Base64 of JSON object 
{"recipient-id":"<unique identifier of the receiver>"}>
https://api.sandbox.sahamati.org.in/proxy/v2