Approve campaign application
Approves a pending application. Same as Accept on the dashboard Applications tab: the creator is added to the campaign, gets the acceptance email, and campaign_affiliate.activated fires. Idempotent: approving an already approved application returns 200 with changed false.
POST
Approves a pending creator application. This does exactly what Accept does on the dashboard Applications tab:
Only pending applications can be approved. Use List campaign applications to find them. Applications to your child brands’ campaigns work too.
Idempotent: calling this on an application that is already accepted returns
403: read-only API key
404: application not found for your organization
422: application is not pending
Returned when the application was already denied, canceled, or is waiting on payment.
422: campaign is completed or canceled
- the creator is added to the campaign as an active creator, with their discount code and link set up the same way as any other accepted creator
- the creator gets the campaign’s acceptance email (and contract, when the campaign uses one)
- the
campaign_affiliate.activatedwebhook event fires, echoing any attribution you sent when the application was created - the decision shows in your activity log
Requires a full-access API key (read-only keys are rejected).
200 with "changed": false and does nothing, so retries are safe. To decide many applications at once, use Bulk approve (up to 50 per request), which also keeps you well inside your hourly request limit.
Path parameters
No request body is needed.
Request example
Response example
Response fields
Error responses
401: missing or invalid API keyAuthorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The application id (the invitation_id returned when the application was created, or id from List campaign applications)
Response
Application approved