References

REST API

Query the registry with simple HTTP requests. No auth required.

Download the OpenAPI 3.1 specification for parameter and response schemas. Unknown parameters, and sort, verified, limit or offset values the API does not recognise, are ignored rather than rejected; a category or type no program has returns an empty list; an unknown slug or API path returns HTTP 404. Errors use { "error": { "code": "...", "message": "...", "hint": "..." } }; the submission endpoints answer { "error": "...", "message": "...", "field": "..." } instead, where field names the input to fix.

Endpoints

GET
/api/programs

List all programs (?q=, ?category=, ?type=, ?verified=, ?include_description=, ?sort=, ?limit=, ?offset=)

GET
/api/programs/{slug}

Get program details by slug, with its OAS (score, grade, report link) when it is scored

GET
/api/categories

List all categories with program counts

POST
/api/submissions

Submit a missing program: the brand's own program page, queued for a maintainer to verify the terms. Not instant; nothing is listed or scored until verified. Returns 202 with an id and statusUrl, or 200 when the domain is already listed or queued. Rate limited per address and per domain (429 with Retry-After). ({ "programUrl": "https://brand.com/affiliates", "termsUrl"?, "name"?, "contact"? (never shown), "note"? })

GET
/api/submissions/{id}

A submission's status: queued, verifying, listed (with listingUrl and, once scored, reportUrl) or rejected (with a reason)

Example

cookieDays and the payout fields are left out when a program does not publish them. For a program with verified false, cookieDays, approval, approvalTime and payoutMethods are left out and payout is an empty object until its terms are checked against the program's own page, and sentences of its free text that state them are dropped; its commission is returned but unconfirmed. Programs with status paused, discontinued or no_program are returned by slug but not in search results or category counts.

curl
curl "https://openaffiliate.dev/api/programs?q=database&type=recurring&verified=true"

# Response (abbreviated)
{
  "programs": [
  {
    "slug": "supabase",
    "name": "Supabase",
    "commission": { "type": "recurring", "rate": "10%" },
    "cookieDays": 60,
    "category": "Database",
    "verified": true,
    ...
  }
  ],
  "total": 1,
  "filters": { "q": "database", "category": null, "type": "recurring", "sort": "relevance" }
}

Brands with no affiliate program

status no_program means no public affiliate program could be found on the brand's own site; discontinued means the brand closed it. GET /api/programs/{slug} still answers for these, with the same shape as any program so existing clients keep working, but with no terms in it:

  • commission is a placeholder: type "none", rate "No affiliate program", mode "unknown", value null. payout is an empty object. Cookie, signup, approval and restriction fields are left out.
  • answer is the page's answer: "No (checked <date>).", then the source and quote from statusNote.
  • alternatives lists verified programs in the same category that pay cash, each with slug, name, commission and url. It can be empty.
curl
curl "https://openaffiliate.dev/api/programs/openrouter"

# Response
{
  "slug": "openrouter",
  "name": "OpenRouter",
  "status": "no_program",
  "commission": { "type": "none", "rate": "No affiliate program", "mode": "unknown", "value": null, "currency": "USD" },
  "payout": {},
  "answer": "No (checked 2026-10-12). OpenRouter has no public affiliate program. ...",
  "alternatives": [
    { "slug": "kyma-api", "name": "Kyma API", "commission": "12% recurring/18mo", "url": "https://openaffiliate.dev/programs/kyma-api" }
  ],
  ...
}

Versioning

Every response carries an API-Version header, currently 1. A request may send API-Version: 1 to pin it; any other value returns HTTP 400 UNSUPPORTED_API_VERSION. Breaking changes ship only under a new major version; new fields, parameters and endpoints can be added to the current one. A field, parameter or endpoint is deprecated at least 90 days before it is removed: its responses then carry a Deprecation header (RFC 9745) with the date it was deprecated and a Sunset header (RFC 8594) with the date it stops working, and the change is listed in the changelog.