Architect Documentation
  • User Guide
  • SDK Documentation
  • Algos Book
  • Architect Add-In For Excel
  • Introduction
  • Creating an API key
  • Getting started with Python
  • Getting started with Rust
  • Concepts
    • Symbology
    • Orderflow
    • Accounts and portfolio management
    • Systems and connectivity diagram
    • Authentication
    • Pagination
  • SDK Reference
    • Symbology and instrument info
    • Marketdata
    • Order entry
    • Portfolio management
    • Connection management
Powered by GitBook
On this page
  • Futures and perpetuals
  • Aliases
  1. Concepts

Symbology

Symbols identify financial instruments using human-readable identifiers. Architect normalizes symbols across different exchanges, venues, clearing houses, etc. to create a consistent nomenclature across the platform. There are three basic types of symbols:

  • Products are things that you can hold and have a balance or position in, such as stocks, bonds, futures, options, etc. Examples of products include: BTC Crypto, AAPL US Equity, USD, EUR, GC 20250626 CME Future, etc.

  • Tradable products are products that identify a trading pair on an exchange or venue. Examples of tradable products include: BTC Crypto/USD, BTC Crypto/ETH Crypto, AAPL US Equity/USD, EUR/USD, GC 20250626 CME Future/USD, etc.

  • Venues are names for exchanges, clearing firms, etc. Examples of venues include: BINANCE, CME, etc. Venues may sometimes be referred to as marketdata venues or execution venues specifically.

Ultimately, symbols are just string identifiers that try to follow particular patterns, nothing more or less.

Futures and perpetuals

Product names for futures and perpetuals generally include their issuing venue, as derivative contracts aren't usually fungible between venues. For example, "GC 20250626 CME Future" refers to the CME futures contract, and "BTC-USDT BINANCE Perpetual" refers to the Binance perpetual. OCC cleared options are a notable exception.

Aliases

For some venues, we provide traditional aliases for products in addition to their Architect normalized names. On CME, you can also refer to "GC 20250626 CME Future" as "GCM5 CME Future" using traditional futures month codes.

PreviousGetting started with RustNextOrderflow

Last updated 1 month ago