Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
api:markets [2024/01/09 20:15] – chad | api:markets [2025/03/14 02:49] (current) – removed chad | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Market Definition Service ====== | ||
- | |||
- | The T4 system identifies products using a 3-part identifier system: | ||
- | |||
- | | **ExchangeID** | A unique ID representing the exchange. \\ (Note: These are logical groupings, therefore there will be more than one ExchangeID for most exchanges.\\ e.g. '' | ||
- | | **ContractID** | A unique ID representing the specific product group.\\ e.g. '' | ||
- | | **MarketID** | A unique ID representing the contract expiry.\\ e.g. '' | ||
- | |||
- | < | ||
- | |||
- | < | ||
- | |||
- | |||
- | |||
- | ===== Exchanges ====== | ||
- | |||
- | Retrieves a list of exchanges available in the market data system. | ||
- | |||
- | ==== API Endpoint ==== | ||
- | < | ||
- | |||
- | ==== Header ==== | ||
- | Include **Authorization** which should contain a valid bearer token. | ||
- | < | ||
- | |||
- | The JSON response is an array of objects, each representing an exchange with its ID, clearing exchange, and description. | ||
- | |||
- | ==== Response Structure ==== | ||
- | ^ Element | ||
- | | exchangeId | ||
- | | clearingExchange | ||
- | | description | ||
- | |||
- | |||
- | ==== Example JSON Response ==== | ||
- | < | ||
- | [ | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | // ... additional exchanges ... | ||
- | ] | ||
- | </ | ||
- | |||
- | |||
- | ====== Contracts ====== | ||
- | |||
- | The **Contracts** API endpoint retrieves a list of contracts for a given exchange. | ||
- | |||
- | ==== API Endpoint ==== | ||
- | < | ||
- | |||
- | ==== Header ==== | ||
- | Include **Authorization** which should contain a valid bearer token. | ||
- | < | ||
- | |||
- | ==== Parameters ==== | ||
- | ^ Parameter | ||
- | | exchangeID | ||
- | |||
- | ==== Response Structure ==== | ||
- | ^ Element | ||
- | | exchangeID | ||
- | | contractID | ||
- | | contractType | ||
- | | description | ||
- | |||
- | ==== Example JSON Response ==== | ||
- | < | ||
- | [ | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | // ... additional contracts... | ||
- | ] | ||
- | </ | ||
- | |||
- | The JSON response is an array of objects, each representing a contract with its exchange ID, contract ID, type, and description. | ||
- | |||
- | |||
- | ====== Contract Search ====== | ||
- | |||
- | The **Contract Search** API endpoint is used to search for contracts based on a given search query. | ||
- | |||
- | ==== API Endpoint ==== | ||
- | < | ||
- | |||
- | ==== Header ==== | ||
- | Include **Authorization** which should contain a valid bearer token. | ||
- | < | ||
- | |||
- | ==== Parameters ==== | ||
- | ^ Parameter | ||
- | | s | The search query string used to search for contracts. | | ||
- | |||
- | ==== Response Structure ==== | ||
- | The response structure will be an array of contract objects. Each object includes details about the contract found in the search. | ||
- | |||
- | ==== Example JSON Response ==== | ||
- | |||
- | < | ||
- | [ | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | // ... additional results ... | ||
- | ] | ||
- | </ | ||
- | |||
- | |||
- | ====== Markets ====== | ||
- | |||
- | The **Markets** API endpoint retrieves information about markets based on specified criteria, including exchange ID, contract ID, and optionally market ID and strategy type. | ||
- | |||
- | ==== API Endpoint ==== | ||
- | < | ||
- | |||
- | ==== Header ==== | ||
- | Include **Authorization** which should contain a valid bearer token. | ||
- | < | ||
- | |||
- | ==== Parameters ==== | ||
- | ^ Parameter | ||
- | | exchangeID | ||
- | | contractID | ||
- | | marketID | ||
- | | strategyType | ||
- | |||
- | ==== Response ==== | ||
- | |||
- | The JSON response is an array of objects, each representing a market with specific details such as exchange ID, contract ID, market ID, description, | ||
- | |||
- | ^ Element | ||
- | | exchangeID | ||
- | | contractID | ||
- | | marketID | ||
- | | description | ||
- | | contractType | ||
- | | expiryDate | ||
- | | lastTradingDate | ||
- | |||
- | ==== Example JSON Response ==== | ||
- | < | ||
- | [ | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | }, | ||
- | // ... additional markets ... | ||
- | ] | ||
- | </ | ||
- | |||
- | |||
- | ====== Market Details ====== | ||
- | |||
- | The **Market Details** API endpoint retrieves detailed information about a specific market based on exchange ID, contract ID, and market ID. This endpoint requires an authenticated user. | ||
- | |||
- | ==== API Endpoint ==== | ||
- | < | ||
- | |||
- | ==== Header ==== | ||
- | Include **Authorization** which should contain a valid bearer token. | ||
- | < | ||
- | |||
- | ==== Parameters ==== | ||
- | ^ Parameter | ||
- | | exchangeID | ||
- | | contractID | ||
- | | marketID | ||
- | |||
- | ==== Response Structure ==== | ||
- | ^ Element | ||
- | | marketID | ||
- | | lastUpdateTime | ||
- | | lastClientUpdateTime | Last update time of market details on the client side. | | ||
- | | description | ||
- | | exchangeID | ||
- | | contractID | ||
- | | expiryDate | ||
- | | lastTradingDate | ||
- | | delistDate | ||
- | | exchangeDelistDate | ||
- | | activationDate | ||
- | | volumeIncrement | ||
- | | numerator | ||
- | | denominator | ||
- | | priceCode | ||
- | | tickValue | ||
- | | orderTypes | ||
- | | contractType | ||
- | | rtsPriceCode | ||
- | | rtsNumerator | ||
- | | rtsDenominator | ||
- | | rtsTickValue | ||
- | | marketRef | ||
- | | legs | Details of the contract legs. | | ||
- | | realDecimals | ||
- | | clearingDecimals | ||
- | | group | Group identifier for the market. | ||
- | | marketRef2 | ||
- | | details | ||
- | | vtt | Variable pertaining to the market. | ||
- | | underlyingMarketID | ||
- | | maintIntraMargin | ||
- | | maintMargin | ||
- | | maintVolScan | ||
- | | minPriceIncrement | ||
- | | pointValue | ||
- | | securityGroup | ||
- | | exchangeDetailsJSON | ||
- | | messageType | ||
- | | messageCategory | ||
- | | messageVersion | ||
- | |||
- | ==== Example JSON Response ==== | ||
- | < | ||
- | { | ||
- | " | ||
- | " | ||
- | " | ||
- | // ... other properties as outlined in the response structure ... | ||
- | } | ||
- | </ | ||
- | |||
- | The JSON response provides detailed information about the specified market, including various attributes like market IDs, dates, margin requirements, | ||
- | |||
- | |||
- | |||
- | |||