Overview
SEBI's algo trading circular (SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013) requires every order placed through an API — not just orders from registered algo strategies — to carry a broker-empanelled Algo ID. This applies whether you're running a formally registered strategy or a personal script hitting the same order endpoints.
ApplicabilityFull enforcement applies from April 1, 2026. Orders placed via the API without a valid, empanelled Algo ID after that date are expected to be rejected at the exchange level, not just flagged after the fact.
What you need to do
- Register your strategy with Shoonya's compliance desk before going live — even a single-user script that trades algorithmically falls under this requirement.
- Receive an Algo ID once your strategy is empanelled with the exchange through Shoonya as the broker.
- Attach the Algo ID to every order placed via Place Order, typically as an additional field in the order payload — confirm the exact field name with your onboarding contact, as it is being finalized across the industry ahead of the deadline.
- Keep static strategies static. Any change to an already-registered strategy's logic may require re-registration — check with compliance before deploying a materially changed version under an existing Algo ID.
Who this affects
| Integration type | Algo ID required? |
|---|
| Manual orders via the Shoonya app/terminal | No |
| Personal script placing orders via the API | Yes |
| Vendor platform placing orders on behalf of clients | Yes, per registered strategy |
| Read-only integrations (quotes, positions, order book) | No — Algo ID only applies to order placement |
Best practices
- Start the registration conversation with compliance well before you plan to go live — empanelment is not instant.
- Log the Algo ID alongside every order in your own audit trail; SEBI's framework expects strategy-level traceability, not just account-level.
- If you run multiple distinct strategies from the same account, register and tag each one separately rather than reusing a single Algo ID across unrelated logic.
Notes
This page summarizes the framework as it applies to API integrators; it is not a substitute for the full circular text or Finvasia's own compliance guidance. Confirm current requirements with your API onboarding contact — this is a fast-moving regulatory area ahead of the April 2026 deadline.
Overview
SEBI's algo trading circular (SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013) requires every order placed through an API — not just orders from registered algo strategies — to carry a broker-empanelled Algo ID. This applies whether you're running a formally registered strategy or a personal script hitting the same order endpoints.
What you need to do
Who this affects
Best practices
Notes
This page summarizes the framework as it applies to API integrators; it is not a substitute for the full circular text or Finvasia's own compliance guidance. Confirm current requirements with your API onboarding contact — this is a fast-moving regulatory area ahead of the April 2026 deadline.