Integration path for vendors and platform partners building on Shoonya's API on behalf of their own users.
Overview
Vendors and algo platforms integrating with Shoonya connect via a dedicated OAuth partner flow, separate from an individual user's own Manual Authentication (OAuth). A vendor integration lets your platform's users authenticate against their own Shoonya account without your platform ever handling their raw credentials.
Currently integrated vendors
Vendor
Status
AlgoTest
Integrated
Quantman
Integrated
Quantiply
Integrated
For these vendors, the vendor's own integration handles connectivity at the platform level — individual end users of these platforms do not need to submit a static IP address to trade through Shoonya.
OAuth authorize URL
Vendors initiate the login flow by directing their users to Shoonya's OAuth authorize endpoint, passing the client_id and a state value:
The app key issued to your vendor integration. Replace Your_app_key with your own key.
state
A unique, unguessable value generated by your platform for each login attempt. It is passed back unchanged on the redirect, so you can match the response to the original request and reject any callback with a missing or mismatched value (CSRF protection). It can also be used to identify which of your users started the login.
After the user authenticates, Shoonya redirects back to your registered redirect URL with an authorization code and the same state value. Verify the state first, then exchange the code for an access token — see Manual Authentication (OAuth) for the full code-exchange sequence.
Getting integrated
New vendor integrations require coordination with the API support team before going live — reach out to get an app_key issued and your redirect URL registered.
Generate a fresh state value for every authorize request and validate it on the redirect before processing the authorization code.
If your platform expects order volume near or above the 10 OPS threshold, that needs to be flagged during onboarding as well, since it affects Algo ID classification per user.
Related
See Manual Authentication (OAuth) for the token exchange steps following redirect, and Rate Limits for the quota/compliance context relevant to high-volume vendor traffic.
Overview
Vendors and algo platforms integrating with Shoonya connect via a dedicated OAuth partner flow, separate from an individual user's own Manual Authentication (OAuth). A vendor integration lets your platform's users authenticate against their own Shoonya account without your platform ever handling their raw credentials.
Currently integrated vendors
For these vendors, the vendor's own integration handles connectivity at the platform level — individual end users of these platforms do not need to submit a static IP address to trade through Shoonya.
OAuth authorize URL
Vendors initiate the login flow by directing their users to Shoonya's OAuth authorize endpoint, passing the
client_idand astatevalue:Example:
client_idYour_app_keywith your own key.stateAfter the user authenticates, Shoonya redirects back to your registered redirect URL with an authorization code and the same
statevalue. Verify thestatefirst, then exchange the code for an access token — see Manual Authentication (OAuth) for the full code-exchange sequence.Getting integrated
app_keyissued and your redirect URL registered.statevalue for every authorize request and validate it on the redirect before processing the authorization code.Related
See Manual Authentication (OAuth) for the token exchange steps following redirect, and Rate Limits for the quota/compliance context relevant to high-volume vendor traffic.