POST /api/v2/buyer/advertisers/{advertiserId}/data-delivery-credentials/{name}/validate
Re-runs the destination probe for a single supported object-storage 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
Parameters
Response
status: "PENDING" — the probe runs asynchronously and updates the credential to VALIDATED (success) or FAILED. On failure, statusError carries a human-readable reason. Currently supported destinationType values are GCS, S3, and AZURE_BLOB. Snowflake and Databricks are not supported Data Delivery destinations.
Errors
404 NOT_FOUND—advertiserIddoes not exist, or no credential matchesname.
Related
Advertiser tasks
All advertiser operations
Advertiser overview
Fields, lifecycle, and concepts
Update reporting bucket
Configure offline delivery