Validate 10DLC Campaign Information | Pinnacle

Validate your 10DLC campaign configuration against carrier requirements and compliance rules.

Authentication

PINNACLE-API-KEYstring

API Key authentication via header

Request

This endpoint expects an object.

campaignIdstringRequired

Unique identifier for the campaign.

When validating 10DLC campaigns, it must begin with the prefix dlc_ (e.g., dlc_1234567890)
When validating toll-free campaigns, it must begin with the prefix tf_ (e.g., tf_1234567890)
When validating RCS campaigns, it must begin with the prefix rcs_ (e.g., rcs_1234567890)

Unique identifier for the campaign. - When validating 10DLC campaigns, it must begin with the prefix `dlc_` (e.g., `dlc_1234567890`) - When validating toll-free campaigns, it must begin with the prefix `tf_` (e.g., `tf_1234567890`) - When validating RCS campaigns, it must begin with the prefix `rcs_` (e.g., `rcs_1234567890`)

additionalInfostringOptional

Any additional information you want to provide.

Response

Returns validation results.

errorslist of objects

List of validation errors.

is_validboolean

Whether the campaign is valid or not.

1	import { PinnacleClient } from "rcs-js";
2
3	async function main() {
4	const client = new PinnacleClient({
5	environment: "https://api.pinnacle.sh",
6	});
7	await client.campaigns.dlc.validate({
8	campaignId: "dlc_1234567890",
9	additionalInfo: "Please validate this DLC campaign for 10DLC compliance",
10	});
11	}
12	main();

Authentication

Request

Response

Errors