Understanding campaign creation via API – Numberly

Introduction

Campaign creation can be carried out guided from the platform and programmatically via API.

Details of each parameter required to create a campaign can be found in the documentation:

Creating a campaign allows you to create the campaigns:

For all campaign types (tactical, applicative and trigger api), defined thanks to the type of campaign and the type of schedule
For all channels: email, SMS and push notification
In draft status, editable from the platform, or published, ready to go depending on campaign type.

IDs required to create a campaign refer to information to which the account has access through other endpoints:

Group_id: list of groups from endpoint /settings/groups
Content Id: list of created content accessible from endpoint /content
Tags: list of tags for the various families accessible from the endpoint /settings/tag-families

It is necessary to fill in at least one value for each mandatory family.
Sender: list of senders accessible for each group from the endpoint /settings/groups/{id}/sender
One sender is required for each population active on the client.
optin_id: list of consents accessible for each group from the endpoint /groups/{id}/optins
procedure_id and parameters: lists of targeting procedures accessible for each group from endpoint /groups/{id}/targeting-procedures,
Each targeting procedure is accompanied by its parameters and associated values.

Once the campaign has been created, it is possible to interact with it thanks to the following endpoints:

Find all the information that defines it on the endpoint /campaigns/{id}
Change its draft or published status through the endpoint /campaigns/{id}
To trigger its sending for an api trigger campaign, or on demand from the api, thanks to the endpoint /campaigns/{id}/sends
To retrieve information linked to the status and progress of a send from the endpoint /campaigns/{id}/sends/{send_id}
Find information on the sending of a message for this campaign thanks to the endpoint /messages
To retrieve the content of the message sent thanks to the endpoint /messages/{id}/content
To trigger message sending for an application campaign thanks to the /messages endpoint.
To retrieve messages replied to this campaign thanks to the enpoint /inbounds

Once the campaign has been created and scheduled, you can find it in Sendingly and analyze its performance in Dashboardly