Search & lookups
Company search plus ticker, crypto, name, and ISIN resolution endpoints that return logos with shared tuning parameters.
Discovery routes help when you begin with something other than a bare apex domain:
| Route | Purpose | Example identifier |
|---|---|---|
GET /api/search | Keyword company search (q= + pagination) | ?q=stripe&limit=8 |
GET /api/ticker/{symbol} | Listed equity ticker → logo pipeline | /api/ticker/AAPL |
GET /api/crypto/{symbol} | Crypto ticker → logo pipeline | /api/crypto/BTC |
GET /api/name/{name} | Free-text corporate name heuristic | /api/name/Stripe |
GET /api/isin/{isin} | ISIN-backed lookup where data exists | /api/isin/US0378331005 |
All lookups ultimately resolve into the same logo enrichment graph used by /api/{domain}, so size, format, retina, theme, fallback, greyscale, refresh semantics match the Logo endpoint tables.
Search (/api/search)
- Pass
q(minimum length enforced — see OpenAPI). limitbounds page size (1–20by default envelope).- Authentication aligns with tiered plans — unauthorized traffic may observe stricter quotas.
Returned rows expose stable identifiers downstream systems can hydrate through the domain-based routes.
When to pivot to /api/{domain}
After you obtain a definitive hostname (stripe.com), switch to CDN or /api/{domain} for deterministic caching semantics and clearer embed policies.
Explore live shapes in openapi.json under the Discovery tag.