Company logos and icons come from Massive's Ticker Overview endpoint, GET /v3/reference/tickers/{ticker}, one ticker per call. The image links are on Massive's API, api.massive.com, so pasting one into a browser or an HTML <img> tag returns HTTP 401 instead of a picture. Most common stocks have a logo; ETFs and over-the-counter (OTC) tickers generally have none. The file format also varies from company to company.
Applies to
- Plans: every Stocks plan, from Stocks Basic to Stocks Business, per the Ticker Overview documentation.
- Endpoints: Ticker Overview, GET /v3/reference/tickers/{ticker}, and the image links it returns under https://api.massive.com/v1/reference/company-branding/.
- Asset classes: stocks. The crypto, forex and index tickers X:BTCUSD, C:EURUSD and I:SPX have no branding object.
How to get a company's logo and icon
- Call Ticker Overview for the ticker.
- Read logo_url and icon_url from the branding object inside results.
- Request each image URL with your API key, either as ?apiKey=YOUR_API_KEY on the URL or as an Authorization: Bearer YOUR_API_KEY header.
curl -X GET "https://api.massive.com/v3/reference/tickers/AAPL?date=2026-10-06&apiKey=YOUR_API_KEY"
Response, trimmed:
{
"results": {
"ticker": "AAPL",
"name": "Apple Inc.",
"branding": {
"logo_url": "https://api.massive.com/v1/reference/company-branding/YXBwbGUuY29t/images/2026-10-01_logo.svg",
"icon_url": "https://api.massive.com/v1/reference/company-branding/YXBwbGUuY29t/images/2026-10-01_icon.png"
}
},
"status": "OK"
}
The date=2026-10-06 parameter pins the example: on 6 October 2026, AAPL's branding was the version dated 1 October 2026, which is the date at the start of each file name. Leave date off to get the current version.
Fetch the logo with the key on the URL. -o saves the image and -w prints the HTTP status and the Content-Type header:
curl -X GET -s -o aapl-logo.svg -w "%{http_code} %{content_type}\n" "https://api.massive.com/v1/reference/company-branding/YXBwbGUuY29t/images/2026-10-01_logo.svg?apiKey=YOUR_API_KEY"
Response
200 image/svg+xml
Sending the key in a header instead returns the same image:
curl -X GET -s -o aapl-logo.svg -w "%{http_code} %{content_type}\n" -H "Authorization: Bearer YOUR_API_KEY" "https://api.massive.com/v1/reference/company-branding/YXBwbGUuY29t/images/2026-10-01_logo.svg"
Response
200 image/svg+xml
Logo and icon: what each image is
The Ticker Overview branding object holds two links and no other fields: logo_url, the company's logo, and icon_url, which the Ticker Overview documentation describes as one of the "smaller, square images that represent the company at a glance". The branding object carries no separate version for dark backgrounds.
The file format of a branding image varies by company. Logos are mostly SVG or PNG, occasionally JPEG, and icons are mostly JPEG, with some PNG. AAPL's icon dated 1 August 2026 is a WebP file. A branding image's Content-Type header matches its file extension, so read either one rather than assuming one format.
Which tickers have a logo or icon
Logo and icon coverage in Ticker Overview depends on the type of ticker:
- Common stocks (CS): most have a logo, usually with an icon. Some, such as GOLD, have a logo and no icon, and a few have no branding object.
- American Depositary Receipts (ADRs) on a US exchange (ADRC, market=stocks): most have a logo, usually with an icon, and a few have no branding object.
- ETFs (ETF): generally no branding object. SPY, QQQ, VOO and ARKK have none.
- Over-the-counter (OTC) tickers (market=otc): generally no branding object. The OTC-traded ADRs TCEHY, NSRGY and RHHBY have none.
To check a ticker, call Ticker Overview for it and read the branding object in results. A ticker with a logo and no icon has logo_url and no icon_url, and a ticker with neither has no branding object.
Getting logos for a list of tickers
Getting logos for a list of tickers takes one Ticker Overview call per ticker, because the All Tickers list and the Unified Snapshot return no branding fields. Neither the All Tickers documentation nor the Unified Snapshot documentation lists a branding attribute, and the All Tickers row for AAPL carries these fields:
curl -X GET "https://api.massive.com/v3/reference/tickers?ticker=AAPL&date=2026-10-06&apiKey=YOUR_API_KEY"
Response, with only request_id removed:
{
"results": [
{
"ticker": "AAPL",
"name": "Apple Inc.",
"market": "stocks",
"locale": "us",
"primary_exchange": "XNAS",
"type": "CS",
"active": true,
"currency_name": "usd",
"cik": "0000320193",
"composite_figi": "BBG000B9XRY4",
"share_class_figi": "BBG001S5N8V8",
"last_updated_utc": "2026-10-07T06:11:24.923109962Z"
}
],
"status": "OK",
"count": 1
}
No field in the All Tickers row holds a logo or an icon.
The date in a branding file name changes over time: AAPL's logo had versions dated 1 August, 1 September and 1 October 2026. Call Ticker Overview again to pick up the current version. An older link can keep working: the AAPL logo dated 10 January 2022, from the example response in the documentation, still returns the image.
Logos from a past date
Past logos and icons come from the Ticker Overview date parameter, which returns the branding in effect on that date:
curl -X GET "https://api.massive.com/v3/reference/tickers/AAPL?date=2026-09-01&apiKey=YOUR_API_KEY"
Response, trimmed:
{
"results": {
"ticker": "AAPL",
"name": "Apple Inc.",
"branding": {
"logo_url": "https://api.massive.com/v1/reference/company-branding/YXBwbGUuY29t/images/2026-08-01_logo.svg",
"icon_url": "https://api.massive.com/v1/reference/company-branding/YXBwbGUuY29t/images/2026-08-01_icon.webp"
}
},
"status": "OK"
}
On 1 September 2026, AAPL's branding was the version dated 1 August 2026, and that version's icon was a WebP file.
Branding history in Ticker Overview starts on 1 November 2023 for AAPL, MSFT, NVDA, JPM and KO: date=2023-11-01 returns a branding object and date=2023-10-31 returns none, even though some older image files still download, such as the AAPL logo dated 10 January 2022. The Ticker Overview documentation lists two years of history on Stocks Basic and all history on the other Stocks plans.
Why the image link needs your API key
Branding image links need your API key because they are served by Massive's API at api.massive.com, and the Ticker Overview documentation says of both logo_url and icon_url: "you must provide an API key when accessing this URL". A browser address bar or an HTML <img> tag sends no key, so it gets HTTP 401. A link that carries apiKey= in a page other people load shares your key with each of them.
If you see an error
A branding image requested with no key returns HTTP 401:
curl -X GET "https://api.massive.com/v1/reference/company-branding/YXBwbGUuY29t/images/2026-10-01_logo.svg"
Response, with request_id removed:
{"status":"ERROR","error":"API Key was not provided"}
"error":"API Key was not provided" with HTTP 401 means the image request carried no key. Fix: add ?apiKey=YOUR_API_KEY to the image URL, or send Authorization: Bearer YOUR_API_KEY.
{"status":"ERROR","error":"Unknown API Key"} with HTTP 401 means the key is not one Massive recognizes, usually a typo or a deleted key. Fix: copy the key again from massive.com/dashboard/keys.
A Ticker Overview response with no branding object means Massive has no logo or icon for that ticker on that date, which is usual for ETFs and over-the-counter (OTC) tickers. If a company you expect to have a logo has none, or an image is wrong or out of date, start a chat at massive.com/contact with the ticker and the image URL.
