Skip to main content
POST /api/v2/buyer/advertisers/{advertiserId}/data-delivery-credentials/{name}/validate Re-runs the destination probe (GCS write+delete, warehouse SELECT 1) for a single credential and returns the updated record with a fresh status. Use this after fixing a buyer-side destination access issue — for example, re-granting GCS bucket IAM — without otherwise editing the credential.

​
Request

curl
curl -X POST https://api.interchange.io/api/v2/buyer/advertisers/12345/data-delivery-credentials/acme-warehouse/validate \
  -H "Authorization: Bearer $SCOPE3_API_KEY"

​
Parameters

FieldTypeRequiredNotes
advertiserIdstring (path)YesAdvertiser ID (numeric, as a string)
namestring (path)YesCredential name (unique per advertiser)

​
Response

{
  "credentialId": "cred_789",
  "name": "acme-warehouse",
  "destinationType": "GCS",
  "config": { "type": "GCS", "bucket": "acme-adcp-reports" },
  "status": "PENDING",
  "createdAt": "2025-01-15T10:30:00Z",
  "updatedAt": "2026-06-07T12:00:00Z"
}
The immediate response always has status: "PENDING" — the probe runs asynchronously and updates the credential to VALIDATED (success) or FAILED. On failure, statusError carries a human-readable reason. destinationType is one of GCS, S3, AZURE_BLOB, SNOWFLAKE, DATABRICKS.

​
Errors

  • 404 NOT_FOUND — advertiserId does not exist, or no credential matches name.
See Errors for the full error contract.

Advertiser tasks

All advertiser operations

Advertiser overview

Fields, lifecycle, and concepts

Update reporting bucket

Configure offline delivery