Skip to navigation
Releases

2026-11-03 — Contact Profile Refresh Requests: verification tiers

Added

verification_tier

POST /api/v1/contact_profile_refresh_requests now accepts verification_tier: quick, standard or premium. A request that names a tier:

  • returns email, mobile_number, direct_phone and corporate_phone in contact_data when requested, each with its value, status and verification details;
  • adds tier, delivered, delivery_reason, tier_satisfied, credits_charged, pending_fields and in_progress to each profile;
  • is priced per delivered field, on the tier’s own prices.

A request with no verification_tier keeps its flow, response and prices.

See Verification Tiers.

Idempotent requests from Clay

When every profile carries metadata.clay_row_id, sending the same set of keys again within 15 minutes returns the first request in its current state, whatever else the new one asks for. Nothing new is created or charged. See Defaults and behaviour notes.

Changed

These apply to every refresh request, with or without a tier.

  • cma and personal_email are no longer offered. They are ignored if sent, and neither requested nor charged.
  • requested_attributes entries must be objects, like { "name": "email", "priority_order": 1 }. Any other shape returns 422.

Notes for clients

  • If you send cma or personal_email, remove them. The rest of the request is served without them.