> ## Documentation Index
> Fetch the complete documentation index at: https://www.mill.fyi/llms.txt
> Use this file to discover all available pages before exploring further.

# Use a passkey recovery code

> Consumes one recovery code against an active password-login challenge and creates a recovery-authenticated session.

No signed-in session is required. Endpoint-specific tokens, setup secrets or challenges may still be required.

Consumes one recovery code against an active password-login challenge and creates a recovery-authenticated session.

[Request conventions](https://www.mill.fyi/api-reference/overview.md) · [API keys](https://www.mill.fyi/api-keys.md) · [MCP connections](https://www.mill.fyi/mcp-connections.md)


## OpenAPI

````yaml api-reference/openapi.json POST /api/auth/passkeys/recovery/verify
openapi: 3.1.0
info:
  title: Mill HTTP API
  version: 1.0.6
  description: >-
    All registered task-board, account, OAuth, MCP transport and health
    operations. MCP tool schemas come from runtime validators; account
    operations follow their server handlers. Example data is fictional.
    Generation imports routes without issuing requests or connecting to a
    database.
servers:
  - url: https://mill-api.example.com
security: []
paths:
  /api/auth/passkeys/recovery/verify:
    post:
      tags:
        - Passkeys and recovery
      summary: Use a passkey recovery code
      description: >-
        Consumes one recovery code against an active password-login challenge
        and creates a recovery-authenticated session.


        No signed-in session is required. Endpoint-specific tokens, setup
        secrets or challenges may still be required.
      operationId: post_api_auth_passkeys_recovery_verify
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                challengeId:
                  type: string
                  pattern: ^[A-Za-z0-9_-]{43}$
                code:
                  type: string
                  minLength: 1
                  maxLength: 100
              required:
                - challengeId
                - code
              additionalProperties: false
      responses:
        '200':
          description: >-
            Successful response. Examples are illustrative; field values vary by
            record.
          content:
            application/json:
              schema:
                type: object
                properties:
                  user:
                    type: object
                    properties:
                      id:
                        type: string
                      name:
                        type: string
                      email:
                        type: string
                      role:
                        type: string
                      timeZone:
                        type: string
                      emailVerified:
                        type: boolean
                      dateFormat:
                        type: string
                      timeFormat:
                        type: string
                      notificationPreferences:
                        type: object
                        properties:
                          assignments:
                            type: boolean
                          mentions:
                            type: boolean
                        additionalProperties: true
                      passkeyCount:
                        type: integer
                    additionalProperties: true
                  workspace:
                    type: object
                    properties:
                      id:
                        type: string
                      name:
                        type: string
                      createdAt:
                        type: string
                    additionalProperties: true
                additionalProperties: true
                description: >-
                  Illustrative response shape. Fields can be absent in alternate
                  successful flows; see the operation description and example.
              example:
                user:
                  id: 66666666-6666-4666-8666-666666666666
                  name: Alex Morgan
                  email: alex@example.test
                  role: member
                  timeZone: UTC
                  emailVerified: true
                  dateFormat: day-short-month-year
                  timeFormat: 24-hour
                  notificationPreferences:
                    assignments: true
                    mentions: true
                  passkeyCount: 0
                workspace:
                  id: 55555555-5555-4555-8555-555555555555
                  name: Studio team
                  createdAt: '2027-01-18T09:30:00.000Z'
        default:
          description: >-
            Request failure. Inspect code, message and requestId; respect
            Retry-After on HTTP 429.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security: []
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
            - requestId
          properties:
            code:
              type: string
            message:
              type: string
            requestId:
              type: string

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.