Schedules an asynchronous email-validation job for the supplied contact IDs. Returns 202 Accepted with a Location header pointing at /v3/background-jobs/{jobId} — poll that endpoint for status and the eventual result.
The eligibility filter (team scope + RequiresValidation status) and the credits cap applied here mirror the /estimate semantics. Set acceptPartial = true to schedule whatever credits allow when the team’s balance is below the eligible count.
Documentation Index
Fetch the complete documentation index at: https://docs.reply.io/llms.txt
Use this file to discover all available pages before exploring further.
Authenticate every request with a Bearer token. Pass your Reply API key in the
Authorization header:
Authorization: Bearer <your-api-key>Get your API key from the Reply dashboard: Settings → API Key.
Request body shared by both /estimate and /schedule. Specifies the contacts to validate and an optional partial-credit acceptance flag.
Contact IDs to validate. Must be non-empty, contain at most 10000 items, and every value must be a positive integer.
1 - 10000 elementsx >= 1When true, the schedule call proceeds with min(eligibleCount, creditsAvailable) contacts even if available credits are below the eligible count. When false (default), insufficient credits become a NotEnoughCredits blocker on /estimate and a 400 on /schedule.
Job scheduled successfully
Acknowledgement returned by /v3/email-validations/schedule. The jobId corresponds to a background job — poll /v3/background-jobs/{jobId} for status and result.
Background-job identifier — use with /v3/background-jobs/{jobId} to poll status
Number of contacts scheduled for validation (capped by available credits when acceptPartial = true)
Credits held against the team's quota for this job. Released for any contacts whose validation does not succeed.