Introduction
CubePlus Rest API is set of HTTP API that provides data required to build trading platform.The APIs are independent of programming languages which will help you to develop the application in any programming language. To get started with consuming APIs, please go through the process details below,
CubePlus Rest API: Process
- Login to the Developer Portal and create the app.
- Create an App to Obtain API Keys: After logging in, create a new application within the Developer Portal to generate the necessary API keys for your application.
- Retrieve API Keys and Set Up Authorization: Obtain your API keys, then follow the instructions in the auth section to configure your API requests properly.
- Access APIs: On the top right select your preferred programming language from the dropdown menu, download the SDK, and then refer to the README file within the SDK along with the provided sample code for the APIs.
- Access Websockets: On the top right choose select your preferred programming language from the dropdown menu, download the SDK using the "Download SDK" option and refer to the streaming folder for details on the WebSocket SDK.
CubePlus Rate Limits
- Request Limit: The rate limits are enforced on a per-API, per-user basis.You can send upto 10 requests Per second.
- Instruments: You can subscribe to up to 3,000 instruments per WebSocket connection and receive live quotes.
- Websockets: A maximum of 5 WebSocket connections is allowed per user.
Visit our FAQ page for more information and solutions.
- APIkey - In order to get the API key, please register at developer portal. Once you register with developer portal, an application should be created to generate the API key.
- accessToken - Access token can be received in the response of access-token or individual token service service .
- Bearer token is a unique cryptic string which identifies the user who is making a transaction in CubePlus platform.
- All CubePlus Rest APIs except authorization section requires the bearer token for authorization.
A simple authorization API workflow described below,
