Skip to Content
Getting StartedAPI GuidesSymbol Master Guide

Use Symbol Master to find instruments

Instrument lookup is a prerequisite for reliable market-data and order workflows. Use the Symbol Master files and symbology guidance in the FYERS API Appendix to select the exact identifier required by the API.

Official reference: FYERS API Appendix

Before you begin

Step-by-step workflow

  1. Choose the relevant exchange and segment

    Select the exchange and market segment that contains the required instrument.

  2. Download the latest Symbol Master file

    Open the FYERS API Appendix and download the latest Symbol Master file for the required exchange or segment. Use the Appendix as the source of truth for available files and the documented symbology format.

  3. Filter by instrument, expiry, strike or symbol

    Filter the file using the fields relevant to the instrument type, such as trading symbol, expiry, strike, option type or instrument category.

  4. Select the required identifier

    Use the exact identifier required by the target API. Do not construct identifiers from assumptions when Symbol Master provides the official value.

  5. Validate the identifier with a read operation

    Use a quote or other supported read operation to confirm that the selected identifier resolves correctly.

  6. Use it in data or order workflows

    Pass the validated identifier into the required market-data or trading workflow and retain the instrument metadata for display and checks.

  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.

Common issues

Authentication or permission failure401 Unauthorized

The access token is missing, expired, or the app does not have the required permission. Generate a fresh token and retry the request.

HTTP/1.1 401 Unauthorized
{"s":"error","code":-8,"message":"Could not authenticate the user"}
View Authentication →
Incorrect request inputs400 Bad Request

A required field is missing or invalid (symbol, quantity, side, or product type). Read the response message, correct the payload, then retry.

HTTP/1.1 400 Bad Request
{"s":"error","code":-50,"message":"Please provide valid order parameters"}
View Error Code Reference →
Plan or rate-limit restriction429 Too Many Requests

The request exceeded the plan’s rate limit or an entitlement. Back off before retrying and confirm the Standard vs Prime limits for the API you are calling.

HTTP/1.1 429 Too Many Requests
Retry-After: 1
{"s":"error","message":"Rate limit exceeded"}
Learn exponential backoff →
Temporary network or socket interruptionTimeout

The connection dropped before a response arrived. Check the latest order, position, or socket state before sending the same request again.

Error: socket hang up
ECONNRESET
View WebSocket Overview →

Continue with AI

Last updated on