Retrieves or triggers email finding for a people search result using the trackId returned in the People Search API response.

Important: Each trackId can only be used once. After the first request, the track ID is consumed and subsequent requests with the same ID will fail. The trackId also expires 6 hours after the original people search response.

You may provide an optional webhook URL to receive asynchronous notifications when email finding completes. When the job completes, we POST the result to your webhook URL.

Auto-refund window: A submission that is charged but never delivered is auto-refunded after up to 10 hours (previously 6h). Worst-case time before a STUCK_* refund appears increases accordingly — no request/response shape change.

Rate limits (per token): If a token already has 500 requests in flight, a further submit is rejected with 400 too many pending requests — drain below the cap (or wait for completions), then retry. Higher concurrency (now 10 processed at once) means the queue drains faster than before. Limits are independent per service (export-people-<token> and email-finder-<token>) and per token — separate tokens have separate budgets.

The response includes statistics (total, found) and state (e.g. PENDING) to track progress.

The header Content-Type: application/json must be included in the request.

📘 Webhook Payload: For the full webhook response schema, see Find Emails Webhook Payload.

🔄 Retry: We automatically retry webhook delivery up to 3 times. If you still need to re-trigger it, use Resend Email Finder Webhook.

✅ Email Verification: All emails (SMTP & CATCH_ALL) returned by the API are verified in real time by BounceBan.