Market data and symbols

Rithmic Symbol Format: Verify the Contract and Exchange

Quick answer

Confirm the product, expiry and exchange in the interface that will use the symbol. In the inspected native Quote Board, entering ESZ6.CME in the symbol cell and leaving that cell resolved an ESZ6 / E-Mini S&P 500 quote row. This is a verified lookup for that build and environment, not a universal JSON or platform format.

Educational software guidance. Trading involves risk. Read the financial and information disclaimers.

Read a futures contract code

A contract code commonly combines a product root, expiry-month letter and year. CME's code explanation identifies ES for E-mini S&P 500 and warns that formats vary across platforms. The month-code table includes:

Month Code Month Code
January F July N
February G August Q
March H September U
April J October V
May K November X
June M December Z

Do not construct a contract merely because a month code exists; available expiries vary by product. A single-digit year also needs the current product/date context.

Native quote lookup observed here

  1. Open the desktop Quote Board from the launcher.
  2. Activate an empty Symbol cell in this inspected interface.
  3. Enter the intended contract and exchange in its accepted notation. The observed test used ESZ6.CME.
  4. Leave the cell and verify the resolved description and quote row.
  5. Confirm the product/expiry against current exchange/provider references before using it in a trading workflow.
Actual native Quote Board after ESZ6.CME lookup; resolved Symbol/Description and bid/offer fields outlined, no trade submitted
Actual native Quote Board after ESZ6.CME lookup; resolved Symbol/Description and bid/offer fields outlined, no trade submitted

No order was sent and no front-month selection algorithm was tested. A populated row establishes that this lookup returned quotes, not account permission or a guarantee of future quote availability.

Keep entry formats separate

The native Order Book labels its input Symbol.Exchange, while its Account selector is separate:

Actual empty native Order Book with Symbol.Exchange, Account and Qty controls outlined; no account selected or quantity changed
Actual empty native Order Book with Symbol.Exchange, Account and Qty controls outlined; no account selected or quantity changed

Sierra Chart documents its own dotted symbol format. PickMyTrade's generator can have a separate trading-symbol field and mapping rules. Do not insert native dotted notation into every connector or alert payload by assumption.

Common questions

Is ES1! the same text as ESZ6.CME?

No. A continuous chart label and a specific contract identifier are different. Confirm the execution contract.

Can I always type the dotted format?

It worked in the observed native lookup. Use the current instructions for each other interface.

Does a valid quote symbol prove I can trade it?

No. Trading permissions, account and order route are separate.

Is a complete symbol-search dialog verified here?

No. This article documents direct cell lookup. It does not invent a search-button location or a complete current expiry list.

Financial and information disclaimers

Financial disclaimer

These guides explain software and workflows. They are for education, not financial, investment, tax, or legal advice. No example is a suggestion to buy or sell a product or use a trading strategy. Trading futures involves substantial risk and can lose money, including all funds you put at risk. Leverage can cause losses that exceed your starting funds. Automation can fail, send duplicate orders, or act late. Stop orders do not guarantee execution or a specific exit price; their behaviour depends on the order type and applicable exchange rules. Review your orders and positions, and consult a qualified professional for your own situation. Paper trades, examples, and past results do not predict live results or promise a profit.

Information disclaimer

This is general help based on the sources and check date shown on each page. Screens, settings, fees, data access, server names, error wording, menu paths, and product support can change or differ by app version, account, country, broker, prop firm, and FCM. The content may contain errors or become out of date; accuracy, completeness, and continuous service are not guaranteed. Check current Rithmic, broker, prop firm, and platform instructions before acting. Screenshots show where controls are located; they do not prove that an order test passed. These guides do not replace broker terms or risk notices. References to Rithmic, RTrader Pro, CME Group, NinjaTrader, Tradovate, TradingView, Apex, Topstep, TradeDay, Leeloo, Bulenox, Earn2Trade and other brands identify their products and do not imply any endorsement of this guide.

Documentation only. Live trading workflows are not certified or execution-tested.

Automate TradingView alerts to Rithmic

See the Rithmic integration