Skip to main content
Each scope is a door on your key: verify email, phone, or CPF. They are separate from send scopes — a list-hygiene key does not need email:send or whatsapp:send.

​
Scopes

Routes covered:
  • Email: POST /v1/validations/email, POST /v1/validations/email/batch, GET /v1/validations/email/batch/{jobId}
  • Phone: POST /v1/validations/phone, POST /v1/validations/phone/batch, GET /v1/validations/phone/batch/{jobId}
  • CPF: POST /v1/validations/cpf, POST /v1/validations/cpf/batch, GET /v1/validations/cpf/batch/{jobId}
Validation scopes are independent from send channels:
  • validations:email ≠ email:send
  • validations:phone ≠ sms:send or whatsapp:send

​
Common combinations

​
Where to configure

  1. Dashboard → Developer → API Keys — check Validations → Verify emails, Verify phones, and/or Look up CPF
  2. OAuth apps — include validations:email, validations:phone, and/or validations:cpf in authorized scopes
In the dashboard (add-ons), verification uses the user session — it does not consume API Key scopes.

​
Next steps