Skip to main content
GET
Fetch the check-address result (charged once on success)
Auth: Required · Billing: the check’s price, charged once here — not on submit · Use case: collect the verdict from POST /v2/check-address
Submission is asynchronous: the POST hands back a check_id and a result_url, and this endpoint is where the verdict arrives.

Request

Poll every few seconds. Typical completion is 5-90 s; a cold BFS on a high-degree address can take longer.

Response 200 — the verdict

verdict.tier3_applied / tier4_applied show which depth tiers ran — tier4_applied: false usually means too few transactions for a meaningful BFS, and Tier 0+1+2 still executed. For what decision means and how to act on it, see POST /v2/check-address.

Other responses

404 does not mean “not finished”. It means this key cannot see that check — a wrong id, or someone else’s. A still-running check answers 202.

Billing — charged once, on delivery

The submit call never charges. This endpoint charges on the first 200 it returns for a given check_id, and never again:
  • Poll ten times before completion → ten 202s, no charge.
  • Poll again after the first 200 → same body, still one charge.
  • Check fails (502) → no charge at all.
So a retry loop is safe by construction; you do not need an idempotency key on the poll. (Idempotency-Key belongs on the submit, to avoid starting a duplicate job.)

See also

Authorizations

Authorization
string
header
required

Your aeg_… API key from the dashboard (Account → API tab).

Path Parameters

check_id
string
required

Response

Successful Response

The response is of type Response Check Address Result Check Address Check Id Result Get · object.