This endpoint authenticates a user and provides a token for further API access.
The token must be included in subsequent requests as a Bearer Token in the Authorization header.

Authentication Required:
No authentication required for this endpoint.

Example Request:

POST /Login HTTP/1.1
Content-Type: application/json
            
{
  "user_id": "AB1234",
  "app_key": "your_app_key",
  "secret_key": "your_secret_key",
  "source": "web"
}

Example Successful Response:

{
  "status": 200,
  "message": "Login successful",
  "data": {
    "user_id": "AB1234",
    "exchanges_allowed": ["NseCm", "NseFO", "Bse", "MCX"],
    "products_allowed": ["CNC", "Intraday"],
    "token": "your_access_token"
  }
}

Example Error Response (401 Unauthorized):

{
  "status": 401,
  "message": "Unauthorized: Invalid credentials",
  "data": null
}

Responses:

• 200 OK – Login successful, returns user details.
• 401 Unauthorized – Invalid credentials.
• 500 Internal Server Error – Unexpected error occurred.

The client must provide both a valid authentication token and ClientID in the request:

Example Request:

POST /Logout?ClientID=12345 HTTP/1.1  
Authorization: Bearer {token}  

This endpoint allows an authenticated client to fetch its detailed user profile, including
their registered contact information, trading permissions, and account-related details.

Authentication Required:
A valid Bearer token must be included in the Authorization header.

Example Request:

POST /UserProfile?ClientID=12345 HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Query Parameters:

• ClientID → The unique identifier of the user whose profile is being retrieved.

Responses:

• 200 OK – User profile retrieved successfully.
• 400 Bad Request – Missing or invalid user ID.
• 401 Unauthorized – Authentication token is missing or invalid.
• 500 Internal Server Error – Unexpected failure while retrieving user profile.

Places a new order for the authenticated client. This endpoint requires authentication using a Bearer token.
The client must include the token in the Authorization header:

Example Request:

POST /NewOrder HTTP/1.1  
Authorization: Bearer {token}  
Content-Type: application/json  

Example Request Body:

{
  "client": "AB1234",
  "quantity": 100,
  "price": 1500.50,
  ...
}

Responses:

• 200 OK – Request for new order sent.
• 400 Bad Request – Invalid order details.
• 401 Unauthorized – Missing or invalid authentication token.
• 500 Internal Server Error – Unexpected failure during order processing.

Modifies an existing order for the authenticated client. This endpoint modifies an order for the authenticated client.
Requires authentication using a Bearer token.

Example Request:

POST /ModifyOrder HTTP/1.1  
Authorization: Bearer {token}  
Content-Type: application/json  

Example Request Body:

{
  "client": "AB1234",
  "exchange_order_no": 987654,
  "quantity": 100,
  "price": 1500.50,
  ...
}

Responses:

• 200 OK – Request to modify order sent.
• 400 Bad Request – Invalid modification request.
• 401 Unauthorized – Missing or invalid authentication token.
• 500 Internal Server Error – Unexpected failure during order modification.

Cancels an existing order for the authenticated client. This endpoint cancels an order for the authenticated client.
Requires authentication using a Bearer token.

Example Request:

POST /CancelOrder HTTP/1.1  
Authorization: Bearer {token}  
Content-Type: application/json  

Example Request Body:

{
  "exchange": "Bse",
  "code": "54897"
  "exchange_order_no": "124886566"
  ...
}

Responses:

• 200 OK – Order sent for cancellation.
• 400 Bad Request – Invalid cancellation request.
• 401 Unauthorized – Missing or invalid authentication token.
• 500 Internal Server Error – Unexpected failure during order cancellation.

This endpoint sends all open orders for cancellation for a specific exchange, security, and client.
Only orders matching both exchange and code for the given client will be sent for cancellation.

Cancellation Criteria:

• exchange: The stock/commodity exchange where the orders were placed.
• code: The security identifier (trading symbol code).
• client: The client whose orders should be canceled.

Example Request:

POST /CancelAllOrders HTTP/1.1  
Authorization: Bearer {token}  
Content-Type: application/json  

Example Request Body:

{
  "exchange": "NseCm",
  "code": 123456,
  "client": "AB1234"
}

Response Scenarios:

• 202 Accepted – All matching orders sent for cancellation successfully.
• 200 OK – Partial success: Some orders canceled, others failed.
• 400 Bad Request – Invalid request parameters or missing required fields.
• 401 Unauthorized – Invalid or missing authentication token.
• 404 Not Found – No matching orders found for the given exchange, security, and client.
• 500 Internal Server Error – Unexpected failure during cancellation processing.

This endpoint allows a client to place a new GTT order.

Authentication Required:
The request must include a valid Bearer token in the Authorization header.

Example Request:

POST /NewGttOrder HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Example Request Body:

{
  "client": "AB1234",
  "exchange": "NseCm",
  "code": 123456,
  ...
}

Responses:

• 200 OK – GTT order placed successfully.
• 400 Bad Request – Invalid request parameters.
• 401 Unauthorized – Missing or invalid authentication token.
• 500 Internal Server Error – Unexpected failure while processing order.

This endpoint allows a client to modify an existing GTT order by changing parameters such as trigger price, order price, or quantity.

Authentication Required:
The request must include a valid Bearer token in the Authorization header.

Example Request:

POST /ModifyGttOrder HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Example Request Body:

{
  "gtt_order_id": 987654321,
  "client": "A125",
  "side": "Buy",
  ...
}

Responses:

• 200 OK – GTT order modified successfully.
• 400 Bad Request – Invalid request parameters.
• 401 Unauthorized – Missing or invalid authentication token.
• 500 Internal Server Error – Unexpected failure while modifying the order.

This endpoint allows a client to cancel a GTT order that has not yet been triggered.

Authentication Required:

• The request must include a valid Bearer token in the Authorization header.

Example Request:

POST /CancelGttOrder?ClientID=AB1234&GttOrderNo=987654321 HTTP/1.1  
Authorization: Bearer {token}  
Content-Type: application/json  

Notes:

• Only pending GTT orders can be canceled.
• If the order has already been triggered or executed, it cannot be canceled.

Responses:

• 200 OK – GTT order canceled successfully.
• 400 Bad Request – Invalid request parameters.
• 401 Unauthorized – Missing or invalid authentication token.
• 404 Not Found – The specified GTT order does not exist or is not cancelable.
• 500 Internal Server Error – Unexpected failure while canceling the order.

This endpoint allows a client to submit multiple orders as a basket in a single request.
The basket ensures that all orders belong to the same client before processing.

Atomic Execution:

• The basket will execute in an atomic fashion within the Risk Management System (RMS).
• All orders must pass or all orders will fail.
• If even a single order in the basket fails due to margin constraints or RMS validation,
  the entire basket will be rejected.

Authentication Required:
The request must include a valid Bearer token in the Authorization header.

Example Request:

POST /ExecuteBasket HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Example Request Body:

{
  "client": "AB1234",
  "orders": [
    {
      "exchange": "NseCm",
      "code": "123456",
      "side": "Buy",
      ...
    },
    {
      "exchange": "Bse",
      "code": "789012",
      "side": "Sell",
      ...
    }
  ]
}

Validation Rules:

• client must be valid and authorized.
• orders list cannot be empty or null
• orders list cannot have more than 20 orders.
• Each order within the basket must belong to the same client.

Example Response:

{
  "status": 200,
  "message": "Basket sent for execution",
  "data": null
}

Responses:

• 200 OK – Basket sent for execution.
• 400 Bad Request – Invalid request parameters (e.g., missing or empty orders).
• 401 Unauthorized – Missing or invalid authentication token.
• 500 Internal Server Error – Unexpected failure while submitting the basket.

Notes:

• Atomic Processing: If any order in the basket fails, the entire basket is rejected.
• RMS Checks: Orders must pass margin and compliance validation.
• If validation fails, an appropriate error message is returned.
• If execution fails, a 400 Bad Request is returned with a failure reason.

This endpoint allows the client to fetch their current and past orders based on filters.

Authentication Required:
The request must include a valid Bearer token in the Authorization header.

**Example Request **

POST /OrderBook?ClientID=AB1234&Filter=Pending HTTP/1.1  
Authorization: Bearer {token}  
Content-Type: application/json  

Query Parameters:

• ClientID → The client identifier whose orders need to be retrieved.
• Filter → Filter criteria for the order book. Allowed values:
  • "All" → Retrieve all orders.
  • "Pending" → Orders that are yet to be executed.
  • "Unconfirmed" → Orders awaiting exchange confirmation.
  • "Cancelled" → Orders that were canceled.
  • "Rejected" → Orders that were rejected.
  • "Failed" → Orders that failed due to validation or RMS checks.
  • "Executed" → Successfully executed orders.

Example Successful Response (200 OK):

{
  "status": 200,
  "message": "Order book retrieved successfully",
  "data": [
    {
      "exchange": "NseCm",
      "symbol": "RELIANCE",
      "side": "Buy",
      ...
    }
  ]
}

Example Error Response (400 Bad Request - Invalid Query Parameter):

{
  "status": 400,
  "message": "Invalid filter value. Allowed values: All, Pending, Unconfirmed, Cancelled, Rejected, Failed, Executed.",
  "data": null
}

Responses:

• 200 OK – Order book retrieved successfully.
• 400 Bad Request – Invalid parameters.
• 401 Unauthorized – Missing or invalid authentication token.
• 404 Not Found – No orders found for the given client.
• 500 Internal Server Error – Unexpected failure while fetching data.

This endpoint allows a client to fetch the latest status of an order placed on the exchange.

Authentication Required:
The request must include a valid Bearer token in the Authorization header. If exchange_order_no = 0 or null or empty, then sender_order_no will be used.

Example Request:

POST /OrderStatus HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Example Request Body:

{
  "client": "AB1234",
  "exchange": "NseCm",
  "exchange_order_no": "987654321",
  ...
}

Responses:

• 200 OK – Order status retrieved successfully.
• 400 Bad Request – Invalid request details.
• 401 Unauthorized – Missing or invalid authentication token.
• 404 Not Found – No order status found.
• 500 Internal Server Error – Unexpected failure while fetching order status.

Fetches all GTT (Good Till Triggered) orders for a given client.

Authentication Required:
The request must include a valid Bearer token in the Authorization header.

Example Request:

POST /GttOrdersBook?ClientID=AB1234 HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Example Successful Response (200 OK):

{
  "status": 200,
  "message": "GTT orders book retrieved successfully",
  "data": [
    {
      "gtt_order_no": 987654,
      "exchange": "NseCm",
      "code": "RELIANCE",
      ...
    }
  ]
}

Example Error Response (400 Bad Request - Missing Client ID):

{
  "status": 400,
  "message": "Missing required parameter: ClientID.",
  "data": null
}

Responses:

• 200 OK – GTT orders book retrieved successfully.
• 400 Bad Request – Invalid or missing query parameters.
• 401 Unauthorized – Client not authorized.
• 404 Not Found – No GTT orders found.
• 500 Internal Server Error – Unexpected failure.

Fetches all executed trades for a given client.

Authentication Required:
The request must include a valid Bearer token in the Authorization header.

Example Request:

POST /TradeBook?ClientID=AB1234 HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Example Successful Response (200 OK):

{
  "status": 200,
  "message": "Trade book retrieved successfully",
  "data": [
    {
      "exchange": "NseCm",
      "code": "RELIANCE",
      "symbol": "RELIANCE",
      ...,
    }
  ]
}

Example Error Response (400 Bad Request - Missing Client ID):

{
  "status": 400,
  "message": "Missing required parameter: ClientID.",
  "data": null
}

Responses:

• 200 OK – Trade book retrieved successfully.
• 400 Bad Request – Invalid or missing query parameters.
• 401 Unauthorized – Client not authorized.
• 404 Not Found – No trades found.
• 500 Internal Server Error – Unexpected failure.

Fetches the complete history of orders placed by a given client.

Authentication Required: Bearer token
If exchange_order_no = 0 or null or empty, then sender_order_no will be used.

Example Request:

POST /OrderHistory HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Example Request Body:

{
  "client": "AB1234",
  "exchange": "NseCm",
  "code": "500325",
  ...
}

Example Response (200 - Success):

{
  "status": 200,
  "message": "Order history retrieved successfully",
  "data": [
    {
      "exchange": "NseCm",
      "symbol": "RELIANCE",
      "side": "Buy",
      ...
    }
  ]
}

Error Responses:

• 400 Bad Request – Invalid parameters.
• 401 Unauthorized – Client not authorized.
• 404 Not Found – No order history found.
• 500 Internal Server Error – Unexpected failure.

Example Error Response (400 - Bad Request):

{
  "status": 400,
  "message": "Invalid request parameters.",
  "data": null
}

Example Error Response (404 - No Records Found):

{
  "status": 404,
  "message": "No order history found.",
  "data": null
}

Fetches all holdings for a given client.

Authentication Required: Bearer token

Example Request:

POST /Holdings?ClientID=AB1234 HTTP/1.1
Authorization: Bearer {token}
Content-Type: application/json

Query Parameters:

• ClientID → The client identifier whose holdings need to be retrieved.