Migrating from 0.7 to 0.10 (beta)
v0.10 is currently still in beta
phase.
Reacher v0.10 introduces the /v1/*
endpoints, namely:
/v1/check_email
: Performs a single email verification while respecting the optional throttle and concurrency settings set in Reacher Configuration (v0.10)./v1/bulk
,/v1/bulk/{job_id}
,/v1/bulk/{job_id}/results
: Create a bulk verification job, and query its progress and status. Docs coming soon.
The /v0/check_email
endpoint DOES NOT change, neither in API nor in behavior. More specifically, even if you specify throttle and concurrency settings in the newly introduced Reacher Configuration, they will not be taken into account by the /v0/check_email
endpoint, which will perform email verification as soon as it receives the request.
Environment Variables
With the introduction of Reacher Configuration (v0.10), some of the Environment Variables have changed names.
Old name | New name | Description |
---|---|---|
|
| The host name to bind the HTTP server to. |
|
| The port to bind the HTTP server to, often populated by the cloud provider. |
|
| If set, bug reports will be sent to this Sentry DSN. |
|
| If set, then all HTTP requests must have the |
|
| Email to use in the |
|
| Name to use in the |
|
| Timeout for each SMTP connection. |
|
| Set to a running WebDriver process endpoint (e.g. |
For Bulk Verification: | ||
|
| |
|
| [Bulk] Database connection string for storing results and task queue |
| Removed | [Bulk] Connections created for the database pool |
| Removed | [Bulk] Minimum number of concurrent running tasks below which more tasks are fetched |
| Removed | [Bulk] Maximum number of tasks fetched at once |
Bulk Verification
The /v0/bulk
endpoints are deprecated, in favor of a RabbitMQ-based queue system. Docs for /v1/bulk
endpoints are coming soon.
Last updated