Provero Logo

Campaigns

Attach a campaign to any API request that creates a validation log so reports stay grouped by project, customer, import source, or workflow.

Set Up First

Create and manage campaigns in Configure → Campaigns before sending them in API requests.

Supported Endpoints

Campaigns are supported on /api/validate/*, /api/fraud-check/*, and /api/validate/multiple.

What To Send

Send either the campaign slug or UUID. In most integrations, the slug is the easier option to read and maintain.

Multi-Validation

For /api/validate/multiple, keep campaign at the top level of the payload so it applies across the nested checks in that request.

If you omit campaign, the request still runs normally. The resulting validation log just won’t be attached to a named campaign in reporting.


Request Body

Field Type Required Description
campaign string No Optional campaign identifier. Send either the campaign slug or UUID from Configure → Campaigns.
Request Payload Example (JSON)
{
    "campaign": "q1-lead-list",
    "email": "test@example.com"
}

Request Examples

Choose language Bash (cURL) 5 examples
curl -X POST https://api.provero.io/api/validate/email \
  -H "Authorization: Bearer REPLACE_WITH_API_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "campaign": "q1-lead-list",
    "email": "test@example.com"
  }'

Response Examples

Choose response example Error - Campaign Not Found 1 examples
{
    "message": "Campaign not found."
}

Response Body

Error structure

Field Name Type Always
Returned
Example Description
message string Yes Returned when the supplied campaign slug or UUID does not exist for the authenticated account.