Massive takes requests for new tickers, datasets and features through its product roadmap rather than through support, and the Submit idea form asks two things: what you would like to be able to do, and how that would help you. Before you ask for a ticker, check that Massive does not already list it under another symbol, because a share class written in a different format can look missing when it is not.
Applies to
- Plans: all plans, including the free Basic plan.
- Endpoints or feeds: /v3/reference/tickers, to check whether a ticker is already listed.
- Asset classes: all.
How to ask Massive to add a ticker, dataset or feature
- For a ticker, search the All Tickers endpoint by company or coin name first, as in the example below. If the ticker is there, you do not need to request it.
- Open the product roadmap and look through it. The roadmap shows ideas under consideration, planned and released, so your request may already be there.
- Click Submit idea on the roadmap page. Say what you would like to be able to do and how it would help you, and name exactly what is missing: the ticker and the exchange it trades on, or the dataset, endpoint or field.
The ticker search below looks for Berkshire Hathaway among stocks:
curl -X GET "https://api.massive.com/v3/reference/tickers?market=stocks&search=Berkshire%20Hathaway&apiKey=YOUR_API_KEY"
Response, trimmed:
{
"results": [
{
"ticker": "BRK.A",
"name": "Berkshire Hathaway Inc.",
"active": true
},
{
"ticker": "BRK.B",
"name": "BERKSHIRE HATHAWAY Class B",
"active": true
}
],
"status": "OK",
"count": 2
}
The class B shares are listed as BRK.B, with a dot, so a request to add BRK-B or BRKB would be a request for a ticker Massive already has. Why are ticker symbols with dashes not showing in Massive's system? covers the symbol conventions behind cases like this. The search parameter matches the ticker and the company name. OTC stocks sit under market=otc rather than market=stocks, and leaving market out searches every market, as the All Tickers documentation describes. An empty results array means no active ticker matches. To search delisted tickers instead, add active=false, which returns only inactive tickers.
Data issues go to support, not the roadmap
A data issue, meaning a wrong, missing or malformed record in data Massive already carries, goes to support rather than to the roadmap, because someone has to look at that record. Start a chat at massive.com/contact with the details listed in How should I go about reporting a possible Massive data discrepancy?
Where a request goes depends on whether Massive already carries the data:
| What you want | Where it goes |
|---|---|
| A ticker Massive does not list, such as a crypto pair that trades on an exchange Massive covers | Product roadmap |
| A field, filter or endpoint that does not exist yet | Product roadmap |
| A dataset Massive does not offer | Product roadmap |
| A missing bar, trade or quote for a ticker Massive lists | Chat at massive.com/contact |
| A value that disagrees with the exchange or with the company's filing | Chat at massive.com/contact |
| A record that comes back with its identifying fields empty | Chat at massive.com/contact |
