Deny campaign application
Denies a pending application. Same as Reject on the dashboard Applications tab: the creator gets the rejection email. Idempotent: denying an already denied application returns 200 with changed false.
POST
Denies a pending creator application. This does exactly what Reject does on the dashboard Applications tab:
Only pending applications can be denied. Use List campaign applications to find them. Applications to your child brands’ campaigns work too.
Idempotent: calling this on an application that is already rejected returns
403: read-only API key
404: application not found for your organization
422: application is not pending
Returned when the application was already approved, canceled, or is waiting on payment.
- the creator gets the campaign’s rejection email
- any pending free sample requests tied to the application are cancelled
- 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 deny (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 denied