---
title: "Queue an on-demand DNS recheck"
method: POST
path: "/api/v1/connections/{connectionId}/reverify"
tags: ["Connections"]
---

# Queue an on-demand DNS recheck

`POST /api/v1/connections/{connectionId}/reverify`

## 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`)

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.

## Path parameters

- `connectionId` string, required

## Headers

- `DoDomain-Team` string

## Response `202`

Success.

- ReverifyConnectionResponse
  - `accepted` true, required

## Other responses

- `400`: `400 invalid_request` — The request body or query failed schema validation, or a documented capability rule rejected it. `details` carries the field-level report when the failure came from schema validation.
- `401`: `401 unauthorized` — No `Authorization: Bearer` header, or the credential is malformed, unknown, or (for OAuth tokens) fails verification.
- `403`: `403 forbidden` — The OAuth access token was not granted the scope this operation requires. `details.code` is `SCOPE_MISSING` and `details.requiredScope` names the scope. Secret keys (`dd_sk_`) carry no scopes and never see this for a missing scope. The one-click start routes also answer it for a session created without one-click (a Free-plan team's session): no `details`, and the end user falls back to the manual records.
- `404`: `404 not_found` — The addressed resource does not exist, or the caller does not own it — the two collapse to one status on purpose, so an id cannot be enumerated by a caller who does not own it.
- `409`: `409 conflict` — The resource is in a state that forbids the operation — for re-verify, the connection was disconnected and is no longer monitored (`details.reason` is `disconnected`).
- `429`: `429 rate_limited` — Rate limited. `Retry-After` (seconds) is set and `details.retryAfterSeconds` repeats it. Branch on `details.reason`: `request_rate` means the caller is calling too fast (`details.limit` carries the cap), `recently_checked` means this one connection was DNS-checked inside its cooldown.
- `500`: `500 internal` — An unhandled server-side failure. Reported to our error tracker; safe to retry.

---

[API](https://skmtc.dev/dodomain/apis/dodomain-api.md) · [All operations](https://skmtc.dev/dodomain/apis/dodomain-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dodomain/apis/dodomain-api/revisions/44cfb944de58?raw)