Queue an on-demand DNS recheck
Enqueues the same per-connection check the periodic monitor runs, so drift/recovery webhooks fire minutes after a support ticket instead of at the next tick. 202, not 200: the check runs in a worker and the result arrives as a connection.verified / connection.failed webhook, never in this response. accepted: true is deliberate rather than a job id — the check may coalesce with an already-queued job for the same connection.
Request
- Base URL: https://app.dodomain.io
- URL: https://app.dodomain.io/api/v1/connections/{connectionId}/reverify
- Auth: one of:
- HTTP bearer
- OAuth 2 (authorization code, authorization URL https://app.dodomain.io/api/auth/oauth2/authorize, token URL https://app.dodomain.io/api/auth/oauth2/token, scopes: connections:write)
Path parameters
The connection id from GET /api/v1/connections, or the connectionId on a connection.* webhook payload.
Headers
The id of the team this call acts on, from GET /api/v1/teams. Needed only when the credential can use more than one team (an OAuth connection granted several); a secret key has exactly one. A team the credential cannot use is refused 404 TEAM_NOT_FOUND — the same answer whether the team exists or not.
Response
Success.
Changes
No recorded changes to this operation across all 1 revision of this API.