Bearer tokens
Personal access tokens sent as Authorization: Bearer <token> headers. Read-only and read+write scopes.
The Hypemarket API is the same surface that powers the Hypemarket web application, served as JSON when the request asks for it. Anything a user can do in the UI is — in principle — doable via the API.
Resources documented in the Resources section are guaranteed to render JSON today. The rest are being rolled out one resource at a time.
Bearer tokens
Personal access tokens sent as Authorization: Bearer <token> headers. Read-only and read+write scopes.
Organization-scoped
Most resources are nested under /organizations/:id. The token authenticates the user; the URL identifies the brand.
ETags + Pagy
Single resources support conditional GETs. Collections paginate via Pagy headers.
AI-agent friendly
Every page is also available as raw markdown, plus llms.txt and llms-full.txt for retrieval.
# 1. Create a token at https://hypemarket.ai/me/access_tokens (one-time view)export HYPEMARKET_TOKEN="..."
# 2. List the organizations the user belongs tocurl -H "Authorization: Bearer $HYPEMARKET_TOKEN" \ -H "Accept: application/json" \ https://hypemarket.ai/organizations.json
# 3. List collabs for an organizationcurl -H "Authorization: Bearer $HYPEMARKET_TOKEN" \ -H "Accept: application/json" \ https://hypemarket.ai/organizations/3/collabs.jsonhttps://hypemarket.aiFor local development, http://localhost:3000.