Overview

Ready to register your 10DLC brand or campaign or verify your TFN? You're in the right place.

10DLC brand and campaign registration

In addition to the API, you can also create brands and campaigns on the Sinch Customer Dashboard.

The following articles are available to walk you through the process on the dashboard:

• Creating a new 10DLC brand
• Creating a new 10DLC campaign

Authentication

There are two ways to authenticate the Registration API: Basic and OAuth 2.0. The recommended way is via OAuth as it is more secure.

OAuth2.0 authentication

Achieve more secure API authentication with OAuth 2.0 access tokens.

Access tokens are short lived. Typically, they will only last one hour. This is done to keep your data (and ours) safer.

In exchanging credentials, you'll get a long string called an access token. This access token will serve as your bearer token in the authorization header of API calls.

There are two pieces of information needed to obtain an access token: the key ID and key secret corresponding to your project ID.

To get an access token, do the following:

1. Login to the Sinch Client Dashboard to get your access keys. If you're using the beta version of our dashboard, click here instead.
2. Click on New Key and when prompted, enter a display name, then click Confirm.

   Does it have to be a new key?

   Not at all. If you have existing credentials saved, feel free to use them.

3. A Key ID and Key Secret will display. Save the project ID, key ID, and key secret someplace safe.

   Important:

   The key secret is only viewable at the time of initial creation.

   If you accidentally misplace they key secret, no worries! Create a new key.

4. Using the following curl command, get your access token using the key ID and key secret.
   Copy

   Copied

   curl https://auth.sinch.com/oauth2/token \
   -d grant_type=client_credentials \
   -u YOUR_Key_ID:YOUR_Key_Secret

5. You'll see your new access token in the response. Now you're ready to use this token on calls to the API. The access token will be useable for one hour.

Basic authentication

Basic authentication is sent in the authorization header with each call.

No matter the programming language, there are three main components for successful basic authentication in a request:

• The designation of authorization type, which is basic
• The username, which in Sinch's case is YOUR_Key_ID, corresponding to your project
• The password, which is YOUR_Key_Secret, again, corresponding to the project

To use basic auth in an API call, do the following:

1. First, create a new access key in the Customer Dashboard by clicking New Key.If you are using the beta version of the Customer Dashboard, create a new access key here instead.
2. Copy your project ID, key ID, and key secret.

   Important:

   Keep your key secret somewhere safe as it is only viewable upon initial project creation. The project ID and key ID are always readily available in the Customer Dashboard. If you misplace your key secret, simply generate a new key!

3. Use your key ID as the username (sometimes called the client_id) and your key secret as the password (can be referred to as the client_secret) in every call made to a Sinch API.

Base URL

The following URLs can be used by the REST API.

Formats and conventions

Let's take a brief look at some of the formats used in the REST API.

JSON

Requests with invalid JSON will be rejected.

Null values

New features

New features might result in additional request and response parameters. New request parameters will either have a default value or be considered optional to retain backwards compatibility. It's highly recommended to ignore any unexpected parameters when reading JSON in API responses and in callback handlers.