Developers overview
PartnerBoost provides two separate REST-style APIs for different account roles. Pick the one that matches your integration — credentials and endpoints are not interchangeable.
Which API should I use?
| You are… | API | Base URL |
|---|---|---|
| Brand / merchant posting orders, managing partners, uploading datafeeds | Brand API | https://app.partnerboost.com/api/brand |
| Partner / affiliate pulling commissions, building links, syncing catalogs | Partner API | https://app.partnerboost.com/api.php?mod=…&op=… |
Do not mix auth docs
Brand auth uses bid, token, secret, and SHA-256 headers. Partner auth uses a per-channel token only. See role-specific authentication pages — never share a single "PartnerBoost API auth" doc across roles.
Brand API highlights
- Post and update orders (
order/new,order/void,order/effective,order/bonus) - Click and transaction reporting
- Creative and datafeed management
- Partner approval workflows
Auth: Brand API authentication
Partner API highlights
- Transaction and click reports
- Commission settlements and payment history
- Monetization catalog, coupons, product datafeeds
- Amazon-specific endpoints on
amazon-service.partnerboost.com
Auth: Partner API authentication
AI integrations
For LLM-based access without custom API code:
Support
Technical questions: Support@PartnerBoost.com