Place your first order

Follow the examples using the global code switcher — Python, Node.js, Java, or cURL.

This guide explains the full sequence without requiring you to assemble the workflow from separate endpoint pages.

Workflow

1. 1

   Authenticate

   Complete the authorisation flow and generate a valid access token. Keep the token secure and confirm that the app has the permissions required for order placement.

   View Authentication →

   Authorization: app_id:access_token

2. 2

   Prepare your order

   Choose the instrument, side, quantity, product type, order type and price fields required for the trade. Validate the symbol and review the order before submission.

   View Single Order API →

   {
     "symbol": "NSE:SBIN-EQ",
     "qty": 1,
     "type": 1,
     "side": 1,
     "productType": "INTRADAY",
     "limitPrice": 0,
     "stopPrice": 0,
     "validity": "DAY",
     "disclosedQty": 0,
     "offlineOrder": false,
     "orderTag": "tag1",
     "isSliceOrder": false
   }

3. 3

   Submit the order

   Send the order request once. Record the returned identifier and response so the result can be checked without placing a duplicate order.

   View Single Order API →

   Application↓

   Single Order API↓

   Order ID / API response↓

   Order Book / Order Details↓

   Order status↓

   Execution confirmation

   curl -H "Authorization:app_id:access_token" \
     -H "Content-Type:application/json" \
     -X POST -d '{ "symbol":"NSE:SBIN-EQ", "qty":1, "type":1, "side":1, "productType":"INTRADAY" }' \
     https://api-t1.fyers.in/api/v3/orders/sync

4. 4

   Read the response

   Confirm whether the request was accepted or rejected. Do not treat an accepted API request as a completed trade; execution status must be checked separately.

   {
     "s": "ok",
     "code": 1101,
     "message": "Order submitted successfully. Your Order Ref. No.808058117761",
     "id": "808058117761"
   }

5. 5

   Verify the order

   Open the Order Book or request order details using the returned identifier. Check the current status, filled quantity, pending quantity and rejection reason where available.

   View Order Book / Order Details →
6. 6

   Handle rejected or pending orders

   For a rejected order, correct the stated issue before trying again. For a pending order, monitor its status or modify or cancel it according to the trading decision.

   View Modify Single Order → View Cancel Single Order →
7. 7

   Verify the result

   Check the relevant API response and account or market-data state to confirm that the workflow completed successfully. If the result is partial or unsuccessful, review the returned status and message before deciding whether to retry or take another action.

   • Request accepted
   • Order identifier received
   • Order status checked
   • Filled/pending/rejected status understood
   • Execution confirmed where applicable

Common issues

HTTP/1.1 401 Unauthorized
{"s":"error","code":-8,"message":"Could not authenticate the user"}

HTTP/1.1 400 Bad Request
{"s":"error","code":-50,"message":"Please provide valid order parameters"}

HTTP/1.1 429 Too Many Requests
Retry-After: 1
{"s":"error","message":"Rate limit exceeded"}

{"s":"ok","orderStatus":"6","message":"Pending"}

Error: request timed out

Related API reference

Continue with AI

Last updated on August 10, 2026