---
title: "Email a sign-in code"
method: POST
path: "/v1/agent_auth/request_code"
tags: ["Authentication"]
---

# Email a sign-in code

`POST /v1/agent_auth/request_code`

## Request

- Base URL: `https://api.revdoku.com`
- URL: `https://api.revdoku.com/v1/agent_auth/request_code`
- Auth: none required

Sends a six-digit code to an existing account email. The response is the same for every address, so it never reveals whether an account exists. Create new accounts in the browser at https://app.revdoku.com/users/sign_up.

## Request body

- object
  - `email` string, email, required
  - `account_id` string: Select another granted account for this request.
  - `reason` string, nullable: Optional purpose for this action. AI agents should explain intentional reads and changes when known; omit when unknown. Do not include secrets, file contents, or transcripts.

## Response `200`

Success

- object
  - `success` true, required
  - `data` CodeRequested, required
    - `message` string
    - `email` string
    - `expires_in_seconds` integer
    - `fallback_url` string, uri
    - `hint` string

## Other responses

- `default`: Request failed. See error.code. Any 429 or 503 response with Retry-After (for example 503 EMAIL_LABELING_PENDING or 503 EMAIL_INDEX_BUILDING): wait that many seconds, then try the read again. 429 EMAIL_SEND_RATE_LIMITED has no Retry-After. Never retry EMAIL_LOOP_DETECTED.

---

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