Guides
Submit a Program
Add a program, what we check, and how long it takes.
Five ways to add a program
Listing is free. Every way ends in the same place: a program file in the public repository, reviewed by a maintainer.
1. Submit by URL
On the submit page, send your program page. No account is needed. It joins the review queue with a status link; nothing is listed or scored, and no pull request is opened for you, until a maintainer has verified the terms on your page and added the program file. Agents use the same queue through submit_program or POST /api/submissions.
2. Full form
The full form writes the program file for you and opens GitHub, where you create the pull request. You need a GitHub account: GitHub copies the repository to your account before the pull request opens.
3. Pull request
Fork Affitor/open-affiliate, add programs/your-product.yaml and open a pull request. The Contributing page lists the rules the file must pass.
4. Suggest a program
Open a Suggest a program issue with only the link to the program page. A maintainer writes the file. This also needs a GitHub account.
5. Email
Send the link to your program page to hello@openaffiliate.dev. GitHub is faster and shows you where the request stands.
OpenAffiliate lists programs; to track and pay partners, run your program on Affitor.
What a maintainer checks
- Every term comes from the brand's own program page or terms. A listing on a network such as Dub or PartnerStack is not proof on its own; link the page on the brand's domain.
- A term the page does not state is left empty. Do not fill a cookie window, a minimum payout or an approval time the brand does not publish.
- Descriptions are factual: what the product does and what the program pays, without ranking words such as “best” or “reliable”.
- The file passes the automatic checks: schema, registry build and a crawl of the signup URL.
Reviews usually take a few days. A pull request with the program page linked in its description is the quickest to review.
After merge
- The program appears on the site after the next deploy, usually within minutes, as not verified: its commission is marked unconfirmed, and its cookie window, payout and approval stay hidden.
- A maintainer verifies the terms on the program page and marks it verified.
- Once every check is assessed, the program gets an OpenAffiliate Score, a report at
/programs/<slug>/oasand a place on /rankings. There is no instant score.
With an AI agent
An agent should check first. If the program is missing, it sends the brand's own program page with the MCP tool submit_program or POST /api/submissions, and reads the result later with get_submission_status. That only joins the review queue: nothing is listed or scored until a maintainer verifies the terms. An agent with GitHub tools can open a pull request or a Suggest a program issue instead, following the same rules as a person.
curl -s https://openaffiliate.dev/api/programs/your-product
# 404: not listed yet. 200: already listed; read its oas.reportUrl.Correct a listing
Terms changed, or a score looks wrong? Open a Terms changed issue with the URL of the page that states the new terms, or use Report an error on the program's OAS report. See re-checks.