Skip to main content
The Campaigns API lets brands and agencies manage campaigns end-to-end: create and publish campaigns, define the content creators produce, approve creators and their submissions, and read performance and spend data.

​
The campaign flow

  1. Create a campaign in draft with its tasks — the deliverables creators complete.
  2. Publish it. Publishing is a request — the campaign moves to pending_approval while Launchpoint reviews it, then becomes active.
  3. Creators apply. If creator_approval_required is on, you approve or reject each application.
  4. Creators submit content. Each submission lands in your review queue; you approve it (clearing it to post) or reject it with feedback (the creator revises and resubmits).
  5. Approved content goes live as posts, whose engagement metrics refresh periodically.
  6. Track everything through metrics — pipeline, performance, and spend in one call.

​
Campaigns, tasks, and submissions

A campaign is the container: what you’re promoting, which creators can join, and how content gets reviewed and paid. Tasks are the campaign’s deliverables — each one is a brief telling creators what to make: the platforms and formats, instructions, a required caption, sounds to use, whether ad disclosure is required. All creator work happens against a task. The campaign’s settings.completion_mode controls how creators engage with the set of tasks: complete all of them (all_required), commit to exactly one (pick_one), any subset (all_optional), or per-task via each task’s is_required flag (some_required). Submissions are the content itself: one creator’s video (or carousel) for one task, submitted for review before anything goes live. A submission is reviewed — by you, or automatically when the task’s review_mode is autoreview — and either approved or rejected with feedback, in which case the creator can revise and resubmit (same submission, higher revision_count). Posts are what approved submissions become once published: the live TikTok/Instagram/YouTube/Snapchat post, linked back to its submission and task, with engagement metrics that refresh over time. So the chain is: campaign → task (what to make) → submission (the content, reviewed) → post (live, measured). Creators, submissions, and posts all carry task_id, so you can slice any campaign’s pipeline and performance by deliverable.

​
UGC (Canvas) campaigns vs standard campaigns

Standard campaigns follow the model above: you author a fixed set of task briefs, creators complete them, content is reviewed and posted. Canvas campaigns are Launchpoint’s continuous-UGC mode: instead of a fixed brief, approved creators keep producing videos week over week, volume is capped weekly rather than per task, and briefs can be generated from what creators submit. Through the API, Canvas campaigns are readable with the same objects — campaigns, tasks, submissions, posts all work — but their configuration lives in the dashboard: tasks on a Canvas campaign are write-locked (409), and per-task fields like max_posts_per_creator don’t apply. Campaigns created through the API are always standard campaigns.

​
Campaign status

When a campaign is auto-paused or a publish is denied, status_detail explains why — for example {"kind": "auto_paused", "reason": "billing_issue"}. Billing-related pauses must be fixed in the dashboard before resuming.
Publishing is asynchronous. Configure a webhook (below) to be notified when your campaign is approved instead of polling.

​
Spend

Spend is read-only in the API: each campaign carries spent_cents (total paid to creators, in cents), the metrics report adds an effective CPM, and each creator shows their individual spend_cents. Billing itself is managed in the dashboard. Note that approving a submission commits the creator’s compensation — the spend follows once the content is posted and paid out, and the approval can’t be undone.

​
Brand and agency keys

One API serves both customer types; the key determines visibility:
  • A brand key sees only that brand’s campaigns.
  • An agency key sees campaigns of every brand the agency manages. Listing defaults to all managed brands (filter with brand_id), and creating a campaign requires brand_id.
Every campaign carries brand_id/brand_name, so payloads are identical for both key types. Requesting a campaign outside your key’s scope returns 404.

​
Scopes

API keys carry scopes, chosen when the key is created in dashboard settings: Approvals are a separate scope because approving a submission commits creator compensation — you can give a reporting integration read access without letting it move money. Keys created before version 2026-07 have no campaign scopes; re-scope them in the dashboard.

​
Pagination

List endpoints return { "data": [...], "has_more": true, "next_cursor": "..." }, sorted newest first. Pass next_cursor as starting_after to fetch the next page, with limit between 1 and 100 (default 25).

​
Idempotency

Send an Idempotency-Key header (any unique string, max 255 chars) on Create Campaign and Add Task to retry safely: repeating the request within 24 hours returns the original response with an Idempotent-Replay: true header. Action endpoints (publish, pause, approve, …) are naturally idempotent — repeating one is a no-op that returns the unchanged resource.

​
Rate limits

120 requests per minute per key (bursts up to 20/s). Every response carries X-RateLimit-Limit and X-RateLimit-Remaining; exceeding the limit returns 429 with a Retry-After header.

​
Errors

Errors use the shared shape {"error": <http status>, "message": "...", "code": "..."}. The code field is machine-readable — the important ones:

​
Webhooks

Instead of polling, configure a webhook URL to receive events across the whole flow — campaign status changes, creator applications and decisions, submissions and reviews, and live posts with metric refreshes. See Webhooks for the full event catalog, signature verification, and retry behavior.

​
Parity with the dashboard

The API covers everything you configure in the dashboard’s campaign editor: campaign info, visibility, creator targeting, links, example videos, and the full task brief (captions, ad disclosure, sounds, automatic review). Campaigns are editable in every status except completed, just like the dashboard. A few dashboard features are intentionally not in the API: creator compensation and billing, product seeding (shipping or gifting products to creators — it depends on the Shopify integration, so configure it in the dashboard for now), paid-ads boosting, organic warm-up, and Canvas campaign configuration (see UGC campaigns above).

​
Conversions

Affiliate code and conversion reporting is not part of this version. A campaign-level codes and conversions report is planned for a future version.