Why Futures Contract Codes Differ Between Exchange Documents and APIs
Summary
The document explains why a futures product may appear with different letter casing in public exchange materials and trading software. Using Shanghai Futures Exchange rebar as its example, it distinguishes the public-facing symbol from the machine-readable instrument identifier used by the CTP interface and VeighNa. Because the identifier is case-sensitive, software users need to enter the form expected by the relevant interface.
It also notes that domestic exchanges do not all follow one casing convention: some interfaces use uppercase product codes, while others use lowercase codes. VeighNa follows the technical naming convention supplied by each exchange interface. This is practical guidance for identifying and querying contracts, rather than a trading strategy. The explanation focuses on code casing and gives examples, but it does not cover complete contract-symbol formats, expiry handling, or how conventions may vary across interface versions.
Key ideas
- Public exchange symbols and API instrument identifiers can use different letter casing.
- CTP instrument identifiers are case-sensitive, so exact spelling matters when querying contracts.
- Domestic futures exchanges follow differing technical naming conventions.
- VeighNa uses the naming conventions exposed by the exchange interfaces it supports.
- The examples explain casing differences but do not describe full contract-symbol parsing.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.