Documentation menu
POST/v1/keys/self/email/verify
Access and price
| Auth | An API key, as Authorization: Bearer snk_… or ?api_key=snk_…. Not metered: it draws no quota and no credit. Needs a full key; a browser (maps) key is refused. |
|---|---|
| Price | Not metered: no quota, no credit. |
What it does
Only the key that asked for the code can redeem it. An address that
already has ANY identity row is NEVER attached, whether or not anybody
ever verified it, and nothing moves between identities: the answer is
409 email-in-use. The app should then sign in with that address
through POST /v1/keys, which the owner's own mailbox verifies; that
is a new key on the address's identity, so the email-less key's own
state (its usage, styles and jobs) does not come with it. A wrong code counts against
identity::MAX_EMAIL_CODE_ATTEMPTS (then the code is void), and
attempts are capped per key and per IP per day like every other
verification budget.
Call it
curl -fsS -X POST "https://api.mapmap.ai/v1/keys/self/email/verify" \
-H "Authorization: Bearer $MAPMAP_KEY" \
-H "Content-Type: application/json" \
-d '{"code":"string"}'Request body
application/json · VerifyEmailCodeRequest
| Field | Type | Required | Description |
|---|---|---|---|
| code | string | yes | The code from the mail. |
Example: A request assembled from this schema's own field examples, enums, defaults and types; not a recorded call
{
"code": "string"
}Responses
verified on the free tier| Field | Type | Required | Description |
|---|---|---|---|
| string | yes | The address now on the account. | |
| monthly_quota | integer | yes | Requests allowed per calendar month from now on. |
| state | string | yes | Always verified. |
Example: A response assembled from this schema's own field examples, enums, defaults and types; not a recorded call
{
"email": "string",
"monthly_quota": 0,
"state": "string"
}application/problem+json · Problem
unauthorized)application/problem+json · Problem
maps-scoped) key on a route that needs a full-scope key (scope-insufficient)application/problem+json · Problem
key-has-email: the key already has an email; email-in-use: the address belongs to another account, which is left untouchedapplication/problem+json · Problem
text/plain
application/problem+json · Problem
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 verify_email_code