v53

latestOpenAPI 3.1.1raw.githubusercontent.com2026-07-264065213.4 KB

Campaigns

Retrieve a campaign

Retrieves a Campaign object.

get/campaigns/{id}

Path parameters

idstring required

The ID of the campaign to retrieve.

Example:cpn_01k0qczvhbet4azgn5xm2ccfst

Response

Campaign

consent_flowstring required

A string explaining the method through which end users will opt in to receive messages from the brand. Typically this should include URLs for opt-in forms or screenshots that might be helpful in explaining the flow to someone unfamiliar with the organization's purpose.

descriptionstring required

An explanation of the organization's purpose and how it will be using text messaging to accomplish that purpose.

idstring required

The campaign ID

includesstring[] required

A list of properties that this campaign should include. These properties can be any of the following values:

links - whether the campaign might send links in messages
phone_numbers - whether the campaign might send phone numbers in messages
age_gated - whether the campaign contains age gated content (controlled substances or adult content)
direct_lending - whether the campaign contains content related to direct lending or other loan arrangements

link_samplestring uri

A sample link that might be sent by this campaign. If links from other domains are sent through this campaign, they are much more likely to be filtered by the carriers. If link shortening is enabled for the account, the link shortener URL will be used instead of what is provided. Reach out to support if you would like to disable automatic link shortening.

message_samplesstring[] required

An array of 2-5 strings with examples of the messages that will be sent from this campaign. Typically the first sample should be a compliance message like You are now opted in to messages from {brand name}. Frequency varies. Msg&data rates apply. Reply STOP to opt out. These samples don't necessarily need to be the only templates that will be used for the campaign, but they should reflect the purpose of the messages that will be sent. Any variable content can be reflected by wrapping it in square brackets like [customer name].

privacy_policy_urlstring uri required

The URL of the privacy policy for the brand in question. This may be a shared privacy policy if it's the policy that is displayed to end users when they opt in to messaging.

The current status of the campaign.

terms_and_conditions_urlstring uri

The URL of the terms and conditions presented to end users when they opt in to messaging. These terms and conditions may be shared among all of a platform's customers if they're the terms that are presented to end users when they opt in to messaging.

use_casesstring[] required

A list containing 1-5 types of messages that will be sent with this campaign.

The following use cases are typically available to all brands:

account_notification - For sending reminders, alerts, and general account-related notifications like booking confirmations or appointment reminders.
customer_care - For account support, troubleshooting, and general customer service communication.
delivery_notification - For notifying customers about the status of product or service deliveries.
fraud_alert - For warning customers about suspicious or potentially fraudulent activity.
higher_education - For messaging related to colleges, universities, and school districts outside of K–12.
marketing - For promotional or advertising messages intended to market products or services.
polling_voting - For conducting surveys, polls, or voting-related messaging.
public_service_announcement - For raising awareness about social issues or important public information.
security_alert - For alerts related to potential security breaches or compromised systems requiring user action.
two_factor_authentication - For sending one-time passwords or verification codes for login or password reset.

For access to special use cases not shown here, reach out to support@surge.app.

volume'high' | 'low' required

This will be one of the following:

low - The campaign will be allowed to send up to 2000 SMS segments to T-Mobile customers each day. In this case your platform will be charged for the setup fee for a low volume number upon receipt of the API request.
high - The campaign will be allowed to send up to 200k SMS segments to T-Mobile customers each day, depending on the trust score assigned by The Campaign Registry. Your platform will be charged for the setup fee for a high volume number upon receipt of the API request, and phone numbers will be charged as high volume numbers going forward.

Example response

{
  "consent_flow": "When customers bring in their car for service, they will fill out this web form for intake: https://fastauto.shop/bp108c In it they can choose to opt in to text message notifications. If they choose to opt in, we will send them notifications to let them know if our mechanics find issues and once the car is ready to go, as well as links to invoices and to leave us feedback.",
  "description": "This phone number will send auto maintenance notifications to end users that have opted in. It will also be used for responding to customer inquiries and sending some marketing offers.",
  "id": "cpn_01k0qczvhbet4azgn5xm2ccfst",
  "includes": [
    "links",
    "phone_numbers"
  ],
  "link_sample": "https://l.fastauto.shop/s034ij",
  "message_samples": [
    "You are now opted in to receive repair notifications from DT Precision Auto. Frequency varies. Msg&data rates apply. Reply STOP to opt out.",
    "You're lucky that hundred shot of NOS didn't blow the welds on the intake!",
    "Your car is ready to go. See your invoice here: https://l.fastauto.shop/s034ij"
  ],
  "privacy_policy_url": "https://fastauto.shop/sms-privacy",
  "status": "pending",
  "terms_and_conditions_url": "https://fastauto.shop/terms-and-conditions",
  "use_cases": [
    "account_notification",
    "customer_care",
    "marketing"
  ],
  "volume": "high"
}