Ticker types
US security type codes from the reference source (asset_class stocks, locale us), with their names. /v1/tickers also reports and accepts FUND for mutual funds, BOND for bonds, CRYPTO for crypto pairs, FOREX for currency pairs and INDEX for indices, which this list does not carry. Default order: code ascending. Results are limited to the entitled scope. Served from the OHLC security master, exchange calendars and reference tables. Access requires the operation capability on the API key.
/v1/ticker-types- Required capability
- reference.read
- Data timing
- As published by the source
- Credits
- 5 credits per request.
Parameters
limitintegeroptional · query- Maximum records per page.Default:
100 cursorstringoptional · query- Opaque cursor, expires after one hour; binds filters, order, resolved as_of, account/key and entitlement. Repeat the original query unchanged.
formatstringoptional · query- Response format. csv returns the data rows with a header row, for spreadsheet functions such as IMPORTDATA; nested fields become dotted columns and lists one JSON array cell, the next page cursor is returned in X-Next-Cursor and meta.errors in X-Meta-Errors. A result without rows is the header row alone, listing the documented fields of a row. Default json, or csv when format is omitted and the Accept header ranks text/csv above JSON; a format the Accept header does not admit returns 406 not-acceptable.
jsoncsv
Response fields
Returns data as an array of records. All example values are illustrative.
codestring- Security type code used by /v1/tickers type.
descriptionstring- Type name.
asset_classstring- Asset class the code applies to.
localestring- Market locale.
Response metadata
Responses include meta.timezone. Dataset responses include next_cursor; health and exports have their own metadata. Request tracing uses the X-Request-ID header.
When something goes wrong
An empty data: [] is a successful query with no matching records. Invalid symbols, permissions and malformed parameters produce an RFC 9457 problem with an actionable detail.
Plans
Requires reference.read. Access, recency and history depth come from the plan definitions the API enforces.
| Plan | Access | Recency | History |
|---|---|---|---|
| Free | Included | As published | Not date-bounded |
| Developer | Included | As published | Not date-bounded |
| Pro | Included | As published | Not date-bounded |
| Commercial | Included | As published | Not date-bounded |
| Scale | Included | As published | Not date-bounded |
Free requests are limited to AAPL, NVDA, JNJ, PEP, MSFT, SPY, QQQ.
History is how far back a plan may request. How far records actually go for a symbol is history_from in dataset coverage. Nothing is real-time. Compare plans