Skip to Main Content

For Vendors / Partners

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 Login (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

VendorStatusStatic IP required for end users?
AlgoTestIntegratedNo
QuantmanIntegratedNo
QuantiplyIntegratedNo
GoChartingIn progressNo (once live)
TradetronIntegratedYes — mandatory

For AlgoTest, Quantman, Quantiply, and (once live) GoCharting, 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. Tradetron is the exception: its integration model requires every end user to register a static IP before their orders will be accepted, same as a standalone OAuth user.

OAuth authorize URL

Vendors initiate the login flow by directing their users to Shoonya's OAuth authorize endpoint:

text
https://api.shoonya.com/OAuthlogin/authorize/oauth?client_id=Your_app_key

Replace Your_app_key with the app key issued to your vendor integration. After the user authenticates, Shoonya redirects back to your registered redirect URL with an authorization code, which your backend then exchanges for an access token — see Manual Login (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.
  • Confirm with the team whether your platform's user base falls into the static-IP-required category (like Tradetron) or the exempt category (like AlgoTest/Quantman/Quantiply) — this depends on the specific integration model agreed during onboarding, not solely on request volume.
  • 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.

See Manual Login (OAuth) for the token exchange steps following redirect, and Rate Limits for the quota/compliance context relevant to high-volume vendor traffic.