Campaigns

Campaign lifecycle: list, get, cancel, duplicate, template cleanup.

Campaign lifecycle: list, get, cancel, duplicate, template cleanup.

Prerequisites

  • A bearer token in the Authorization header. Any endpoint that needs no token says so on its own page.
  • The id of each record the call targets. Every endpoint page lists the ids it needs.

Errors

StatusMeaning
401The bearer token is missing, expired or invalid
403The token is valid but the record sits outside your account
422The request failed validation — the response names the fields
500Unexpected server error

Individual endpoints may return more; each page lists its own.

Endpoints

List campaigns

GET — List campaigns for the authenticated user's own company (paginated), with status/search filtering and sorting.

Open →

Get campaign by id

GET — Get one campaign, including its channels, follow-up template, email and SMS requests, and file-header mapping — all in a single response, so you do not need follow-up calls to assemble the full picture.

Open →

Cancel campaign

POST — Cancel a campaign owned by the caller's company by setting its status to cancelled.

Open →

Duplicate campaign

POST — Duplicate a campaign (and its active channels) under the same company as a fresh draft named "… (Copy)" with audience/scheduling fields reset.

Open →

Remove follow-up template

DELETE — Clear the follow-up email template association on a campaign channel by setting its follow_up_template_id to null.

Open →

Create / update campaign (wizard step)

POST — Create or advance a review-solicitation campaign through the 4-step setup wizard, branching on the step field.

Open →

Send review request (test-review-request — deprecated alias)

POST — Create a one-off audience row and queue an Email and/or SMS review request for a campaign (dispatched after DB commit onto the messaging queue).

Open →

Direct-to-company email

POST — Record an internal customer_comment tied to an Email or SMS review request (looked up by unique_code) and emails the resolved recipients (store owner and/or configured manager/other-manager addresses, based on direct_to_option) using the DIRECT_TO_COMPANY template.

Open →

Direct comment feedback

POST — Create an off-platform reviews row plus an internal customer comment tied to an Email or SMS review request (looked up by unique_code), then notifies the store's configured recipients with the CUSTOMER_COMMENT template.

Open →


Did this page help you?