All APIs

Available now

Premium Catch-All Recovery API

Run opt-in recovery for risky catch-all rows in a completed validation job without changing canonical validation status.

Use Premium Catch-All Recovery when a completed CSV validation job has risky catch-all results that need separate recovery confidence and recommended action fields for outbound routing.

Public endpoints

/v1/csv/jobs/{id}/recover-catchalls/v1/csv/jobs/{id}/recovery

Auth header: X-API-Key

Create an API keyRead recovery docs

Use this API when

  • You already have a completed validation job with risky catch-all results and need opt-in recovery guidance.
  • You need confidence and recommended action fields for outbound routing.
  • You want recovery output separate from canonical validation status.

Do not use it when

  • You need deterministic proof that a catch-all mailbox exists.
  • You need a workflow that sends verification emails.
  • You want standard catch-all validation to be charged by default.
bash request
curl -X POST https://api.gtmapis.com/v1/csv/jobs/batch_123/recover-catchalls \
+  -H 'X-API-Key: gtm_test_1234567890abcdef1234567890abcdef'
json response
{
  "email": "alex@example.com",
  "status": "risky",
  "recovery": {
    "confidence": "medium",
    "recommended_action": "manual_review",
    "method": "non_intrusive_scoring"
  },
  "recovery_credits": {
    "consumed": 0
  }
}

Result semantics

  • Recovery fields do not change the canonical risky validation status.
  • Recovery confidence and recommended action are recovery-specific fields.
  • Recovery is non-intrusive and must not send verification emails.

Credit behavior

  • Standard catch-all validation remains transparent and non-chargeable by default.
  • Recovery credit fields are separate from standard validation credit fields.
  • Recovery economics should be evaluated as opt-in recovery behavior, not default validation behavior.

Errors and failures

  • Authentication errors should be resolved with a valid API key sent through X-API-Key.
  • Recovery should be requested only for eligible catch-all/risky validation contexts.
  • Do not treat recovery failure as a canonical valid or invalid mailbox result.

Common questions

Does recovery make a catch-all result valid?

No. Recovery fields do not change the canonical risky status.

Does recovery send verification emails?

No. Premium Catch-All Recovery is non-intrusive and must not send verification emails.

Is catch-all detection charged by default?

No. Standard catch-all validation remains non-chargeable by default.