The Login, Generate OTP, Generate Secret Key, and Generate Access Token APIs are deprecated. Please migrate to the latest V3.2 APIs — use Generate Session Token for direct authentication or OAuth 2.1 Authorization-Code Flow.

The SAMCO Trade API is a set of REST APIs that allows users to build customized applications based on their trading requirements. It enables users to log in, search for symbols, place and execute orders, view order status, and check their positions and holdings, among other functions. This documentation provides all the necessary details to understand the SAMCO Trade API collection. The APIs ship ready-to-run code samples in cURL, Java, Node.js, and Python — see Supported Client Runtimes for tested versions.

For reference, you can download the Postman collection by Click here .

For downloading a list of all tradeable scrips across exchanges please Click here . This is a CSV file which you can import into your database.

APIs will work intermittently over the weekends/holidays and outside market hours due to maintenance activity.

Supports the list of following index names: ​

APIs That Do Not Require Session Token ​

The following APIs can be accessed without a session token:

HTTP Request Header ​

This is the request header which should be included in every API request.

ℹ️ Note: The session token is required for all APIs except the ones listed above.

Http Response Code ​

The HTTP response code indicates the success or failure of an HTTP request. Below is a list

Rate Limits - April 2026 ​

We have implemented two types of rate limits on our server: session-based and IP-based.

Session-based rate limit : When a client logs in, they receive a session token. This token represents one session. For example, if the client is using the personal index API, they can make 3 requests per second with this session token.

IP-based rate limit : If a client is in an organization where many clients are using the trade API, we apply an IP-based rate limit. This means that from that organization's IP address, only a limited number of requests to each API are allowed.

For example, the personal index API has a IP rate limit of 20 requests per second. If 5 employees in an organization are using the personal index API from the same IP address, each employee can make up to 4 requests per second. If any employee exceeds their limit and makes 5 requests per second, one of the requests from the other employees will fail.This means that no client can exceed their session limit, and no client from a single IP address can exceed the IP-based limit.