Submit for review
Submits a finished draft to Oppizi for review.
The campaign stops at In Review. Nothing is charged, and nothing prints or is mailed automatically — an Oppizi reviewer approves it, and production starts after that. There is no API that triggers printing or fulfilment directly.
If anything is missing the call fails and names it; creation status lists what is outstanding.
Needs an OAuth access token carrying the campaigns:create scope — a plain client key is refused. The campaign must be one of yours; anything else returns 404.
Authorization
campaignBuilderOAuth campaigns:createOAuth access token carrying the campaigns:create scope, obtained through the Oppizi consent screen (the same sign-in used by the MCP connector). A plain client key carries no scopes and is refused on these endpoints.
In: header
Scope: campaigns:create
Path Parameters
Your campaign id.
Response Body
application/json
curl -X POST "https://example.com/client/campaigns/string/submit"{ "success": true, "data": { "campaignId": 9700, "status": "IN_REVIEW" }}Read back draft targeting GET
The targeting currently saved on your draft: map zones with their route counts, the carrier routes themselves, and any demographic attributes. This is the read-back for the two targeting steps. It returns everything in one response and takes no paging parameters.
Rename a campaign PATCH
Changes the name of one of your campaigns. Needs an OAuth access token carrying the `campaigns:create` scope — a plain client key is refused. The campaign must be one of yours; anything else returns 404.