External Vets

In some instances, brands need access to special use cases (such as Political or Charity) or want to perform a deeper identity check to potentially get better messaging terms with network carriers. To accomplish this, they need to be vetted by a TCR-approved external vetting provider such as Aegis Mobile, Campaign Verify, or WMC Global. TCR can import existing vetting tokens from a TCR-approved external vetting provider, or accept a new vetting request placed via an API call. The three types of external vets include:

• Standard: Standard vets can be used to verify a brand or potentially gain access to better throughput levels with network carriers. A score is returned which grants a brand access to particular levels of messaging throughput.

• Enhanced: Enhanced vets are typically requested if a user is dissatisfied with their Standard vet score.

• Political: Political vets allow brands to use the Political special use case. Non-Profit brands that have a 501(c)(3/4/5/6) Tax Exempt Status are already granted access to the Political use case and are not allowed to request or import a Political vet from any vendor.

For detailed information on applying for external vets, see the External Vetting Requests using the CSP API documentation.

Order a New External Vet

1. Find the brandId for the brand you wish to vet.

2. Find the evpId for the desired vetting partner by using the GET /enum/extVettingProvider endpoint.

3. Find the desired vettingClass for the type of vet to request using the GET /enum/vettingClass endpoint.

4. Use the POST /brand/{brandId}/externalVetting endpoint to initiate an external vet. Refer to the endpoint for any required information. Political vets require an additional payload.

While this API call will return a message, the actual results of an external vet may take up to 48 hours depending on the type of vet and the vetting provider. When the vetting is complete, the results are recorded in TCR. The brand’s Vetting Status may change to UNSCORE, ACTIVE, or FAILED depending on the result. The status of external vets can be polled by the CSP using the GET /brand/{brandId}/externalVetting endpoint.

Standard Vet Request

POST /brand/{brandId}/externalVetting

curl -X 'POST' \ 
'https://csp-api-staging.campaignregistry.com/v2/brand/B123ABC/externalVetting' \ 
-H 'accept: application/json' \ 
-H 'Authorization: Basic XXXXXXXXXX' \ 
-H 'Content-Type: application/json' \ -d '
  { 
    "evpId": "AEGIS", 
    "vettingClass": "STANDARD" 
  }' 

Standard Vet Response

{ 
  "evpId": "AEGIS", 
  "vettingId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", 
  "vettingToken": null, 
  "vettingScore": null, 
  "vettingClass": "STANDARD", 
  "vettingStatus": "PENDING", 
  "reasons": null, 
  "vettingDetails": {}, 
  "vettedDate": null, 
  "createDate": "2024-10-14T05:35:34.123Z" 
}

Import an Existing Vet

1. Find the brandId for the brand whose vet you want to import.

2. Find the evpId for the vetting partner by using the GET /enum/extVettingProvider endpoint.

3. Locate the vettingId supplied by the vetting partner.

4. Use the PUT /brand/{brandId}/externalVetting endpoint to import the vetting record.

This API call will return a response with the status of the latest vetting record.

Campaign Verify Vet Import Request

PUT /brand/{brandId}/externalVetting

{
  "evpId": "CV",
  "vettingId": "cv|1.0|cvmock|10dlc|###|###",
}

Campaign Verify Vet Import Response

{
  "evpId": "CV",
  "vettingId": "cv|1.0|cvmock|10dlc|###|###",
  "vettingToken": null,
  "vettingScore": null,
  "vettingClass": "POLITICAL",
  "vettingStatus": "ACTIVE",
  "reasons": [],
  "vettingDetails": {},
  "vettedDate": "2025-02-13T16:29:22.000Z",
  "createDate": "2025-02-13T16:29:22.000Z"
}