Create campaign application
Submits an applicant from your own signup form directly into a Growi campaign. Creates the creator account if needed and stores marketing attribution (Meta click ids, UTMs, TikTok enrichment) that is echoed back on outbound webhook events. Idempotent: repeat submissions for the same email + campaign return the existing application.
POST
Submits an applicant from your own signup form directly into a Growi campaign — so you can host the signup experience on your domain while Growi handles creator onboarding, approval, and tracking.
The endpoint creates the creator account if it doesn’t exist yet, files a pending application to the campaign (or accepted, when the campaign auto-accepts applicants), and stores any marketing attribution you send. When the creator is later approved, or generates a sale, the attribution is echoed back on the corresponding webhook events so you can match the creator in your ad platform (for example, forwarding to the Meta Conversions API).
Idempotent: repeat submissions for the same
A repeat submission returns
404 — campaign not found for your organization
422 — validation
Requires a full-access API key (read-only keys are rejected).
email + campaign_id return the existing application with created: false instead of creating a duplicate. Attribution keys not seen before are merged in; existing values are never overwritten. This endpoint is also exempt from the 2-second request-interval limit, so bursts of near-simultaneous form submissions are safe.
Request body
Attribution fields (all optional)
Everything below is stored verbatim and echoed back inside theattribution object on webhook events.
Request example
Response example
200 with the same shape and "created": false.
Response fields
Error responses
403 — plan or keyUse cases
- Host your own signup form: keep the application experience on your domain (with your pixels and analytics firing natively) while applicants flow straight into Growi for review.
- Meta ads attribution: send
fbp/fbc/event_idwith each applicant, then forward thecampaign_affiliate.activatedandaffiliate_sale.createdwebhook events — which echo the same identifiers — to the Meta Conversions API so your media team can optimize on approvals and revenue. - CRM sync: pass your internal applicant
id; it comes back asattribution.external_idon webhook events for painless matching.
Authorizations
Body
application/json