Developers

Experimental logo catalogue API

Read recorded sources, available files and entity relationships. Responses and availability may change. There is no published service-level agreement or paid API tier; handle unavailable services, rate limits and withdrawn files.

Endpoints

GET  /api/v1/logos/{slug}          → catalogue record, file permissions and recorded versions
GET  /api/v1/search?q=bird          → brand, company, designer and country suggestions
POST /api/v1/similar                → form data: image file or q text; not JSON
GET  /api/v1/verify?domain=example.com → catalogue lookup, not live website inspection
GET  /changelog.xml                 → RSS of public archive changes

Example

curl https://similarlogo.com/api/v1/logos/coca-cola

Try it →

Search input and results

For text search, send q of at most 200 characters. Image search accepts a PNG, JPEG, SVG or WebP file of at most 20 MiB in the image field. Matching depends on the configured services and may return available: false. Inspect method and any explanatory message: keyword, exact-file and image-feature results are different kinds of evidence. A score is not identification probability or trademark clearance.

curl -X POST https://similarlogo.com/api/v1/similar -F 'q=blue bird'

Uploaded images are processed by the configured matching services. Do not submit confidential artwork; read the data-handling notice before uploading.

Limits and file use

Operational limits depend on the environment. Handle HTTP 429 and Retry-After when supplied, and back off on temporary service failures. No fixed daily allowance is promised.
On logo records, inspect rights_state, downloadable and each file's delivery/source conditions. A permitted preview does not guarantee an original download.
Files and previews can be withdrawn. No permanent hotlink or change-notification service is promised.
Preserve source attribution and notices. Hosting or downloading a logo does not grant a commercial licence or imply the owner's endorsement.