Docs / API

Requests & authentication

Base URL, HTTP methods, keys, and request conventions.

Base URL

https://brandmarks-api.brandmarks-web.workers.dev
Route Returns Key
GET /v1/logo/{identifier} Image Publishable (recommended) or secret
GET /v1/companies/{identifier} Company object Secret
GET /v1/search?q={query}&limit=10 Search results Secret

All endpoints are read-only. Use GET for integrations; methods other than GET and HEAD are rejected, apart from image OPTIONS preflight. There are no write, batch, or subscription endpoints.

Send JSON requests with Authorization: Bearer YOUR_SECRET_KEY. Image elements use ?token=YOUR_PUBLISHABLE_KEY. A Bearer header takes precedence over the query token. Although the implementation accepts query tokens for JSON, always use a header to keep secret keys out of URLs and logs.

Encode identifiers as a URL path segment with encodeURIComponent; encode search text with URLSearchParams or curl --data-urlencode. Use HTTPS. JSON endpoints are intended for server-side requests, not direct browser access.

There is no pagination cursor or idempotency key. The versioned OpenAPI 3.1 specification describes the current v1 routes, authentication, parameters, response schemas, and error envelope. Its curl examples use placeholder keys; replace them with your issued beta keys. See responses and errors.

Need a hand? Get help · Technical content reviewed October 2, 2026