latestOpenAPI 3.0.1MIT2026-08-102249151.2 KB

9eecb207c30d

10DLC Campaign Registration

Qualify Brand by Use Case

Before submitting a campaign, this API will provide some important feedback about how the resulting campaign will be treated. You can verify that the campaign will be supported by all operators, the AT&T message class and TPM, the T-Mobile brand daily bucket that will be applied and more.

It is suggested to validate that the operator restrictions will meet your needs prior to submitting the campaign request. Brand revettings do not automatically adjust operator restrictions, and in some cases a new campaign may have to be resubmitted to receive the adjusted MNO values.

get/v1/projects/{projectId}/campaignRegistrations:qualify

Path parameters

projectIdstring required

Sinch uses projects to group resources such as contacts and apps together to manage and connect a unique set of keys and secret IDs for all your Sinch API products. To identify a project, it is given a unique alphanumeric identifier that ties it to your account. Your project ID can be found in the Customer Dashboard.

Query parameters

brandIdstring required

Brand Id to be qualified

useCasestring

The desired Use Case.

Response

A successful response.

useCasestring

Desired useCase.

monthlyFeenumber float

Monthly registration fee for campaign. If auto-renew is selected on a campaign, this recurring fee will be charged monthly starting three months after the campaign is submitted.

setupFeenumber float

Initial setup fee, charged immediately once the campaign has been approved by Sinch and submitted to partners. This fee covers the first three months of campaign use, and will be charged whether or not the autoRenewal parameter is set on the campaign.

minSubUseCasesnumber

Minimum number of sub use-cases required when registering a campaign with the desired use case.

maxSubUseCasesnumber

Maximum number of sub use-cases required when registering a campaign with the desired use case.

mnoMetadataobject