Skip to content
Documentation menu
docs / api / post-v1-keys-verify
Keys and account

POST/v1/keys/verify

Access and price

AuthNo key. Not metered.
PriceNot metered: no quota, no credit.

What it does

Confirms the ONE key a link was mailed for, upgrading it to the verified free tier (or the plan already bought). Only an explicit press of the page's button reaches this (review of #1339, H1).

No key. Not metered.

Call it

bash
curl -fsS -X POST "https://api.mapmap.ai/v1/keys/verify" \
  -H "Content-Type: application/json" \
  -d '{"token":"string"}'

Request body

application/json · VerifyTokenBody

FieldTypeRequiredDescription
tokenstringyesThe single-use token from the emailed link (the #t= fragment, or the ?token= query of a link sent before the fragment form).

Example: A request assembled from this schema's own field examples, enums, defaults and types; not a recorded call

json
{
  "token": "string"
}

Responses

200The key is verified (now, or already)
FieldTypeRequiredDescription
monthly_quotaintegernoThe applied monthly quota after a confirmation (a plan bought before confirming is honoured, not the free tier); absent after a refusal.
statestringyesverified after a confirmation, revoked after "This wasn't me".

Example: A response assembled from this schema's own field examples, enums, defaults and types; not a recorded call

json
{
  "state": "string"
}
400Missing, unknown, used or expired token, or the key has been deleted

application/problem+json · Problem

409The account already has five verified keys; revoke one first

application/problem+json · Problem

413The request declares a body larger than 1048576 bytes (plain text, not problem+json)

text/plain

504The request did not finish within the gateway's request deadline (request-timeout)

application/problem+json · Problem

Error bodies follow the shared problem model documented on API conventions.

Also under Keys and account

Generated from https://api.mapmap.ai/openapi.json on 2026-11-18 · operationId confirm_key