Autofill RCS Campaign Information

Generate campaign details based off existing campaign and the brand it's connected to.

Authentication

PINNACLE-API-KEYstring
API Key authentication via header

Request

This endpoint expects an object.
additionalInfostringOptional
Any additional information you want to provide.
campaignIdstringOptional

Unique identifier for the campaign.

  • When autofilling 10DLC campaigns, it must begin with the prefix dlc_ (e.g., dlc_1234567890)
  • When autofilling Toll-Free campaigns, it must begin with the prefix tf_ (e.g., tf_1234567890)
  • When autofilling RCS campaigns, it must begin with the prefix rcs_ (e.g., rcs_1234567890)

Response

Returns autofilled RCS information.
agentobject
Agent configured to the campaign.
brandstring
campaignIdstring
Unique identifier for the campaign.
ctaLanguagestring

Required text that appears next to the opt-in checkbox for your opt-in form. This checkbox has to be unchecked by default. See the CTA Language section for requirements.

ctaMediastring

URL to the opt-in form or a URL to a screenshot of the opt-in CTA.

demoTriggerstring

Instructions on how an external reviewer can trigger messages and an example flow from the agent. This is usually an inbound text message to the agent that will start a flow of messages between the agent and the user. See the Demo Trigger section for requirements.

expectedAgentResponseslist of strings

List of what the agent might say to users. See the Expected Agent Responses section for requirements.

keywordsobject
messagingTypeenum

Type of message the agent sends.

OTP: One time passwords or verification codes.
TRANSACTIONAL: Account updates, alerts, or notifications.
PROMOTIONAL: Marketing, sales, or offers.
MULTI_USE: Mixed message types.

Allowed values:
optInMethodstring

Details on how opt-in is acquired. If it is done through a website or app, provide the link. See the Opt-In Method section for requirements.

trafficobject
useCaseDescriptionstring

Detailed summary of what the brand is and how this agent will be used. See the Use Case Behavior section for requirements.

Errors

400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
500
Internal Server Error