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

# Verify sender

> Start Dench Emailing Service sender verification.



## OpenAPI

````yaml /api-reference/openapi.json post /email/identities/verify
openapi: 3.1.0
info:
  title: Dench API
  version: 1.0.0
  description: >-
    Versioned Dench workspace API. The operation registry is shared with the
    Dench CLI parity layer, so every CLI command maps to an endpoint here.
servers:
  - url: https://www.dench.com/api/v1
security: []
tags:
  - name: agent-config
    description: Agent Config operations.
  - name: approvals
    description: Approvals operations.
  - name: apps
    description: Apps operations.
  - name: auth
    description: Auth operations.
  - name: billing
    description: Billing operations.
  - name: browser
    description: Browser operations.
  - name: chat
    description: Chat operations.
  - name: crm
    description: Crm operations.
  - name: email
    description: Email operations.
  - name: files
    description: Files operations.
  - name: gateway
    description: Gateway operations.
  - name: local
    description: Local operations.
  - name: memory
    description: Memory operations.
  - name: meta
    description: Meta operations.
  - name: routines
    description: Routines operations.
  - name: workspace
    description: Workspace operations.
paths:
  /email/identities/verify:
    post:
      tags:
        - email
      summary: Verify sender
      description: Start Dench Emailing Service sender verification.
      operationId: email_identity_verify
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                type:
                  type: string
                  enum:
                    - domain
                    - email
                  description: >-
                    Identity scope. `domain` verifies via DNS (DKIM); `email`
                    verifies a single mailbox via a confirmation email.
                identity:
                  type: string
                  description: Domain (example.com) or mailbox (founder@example.com).
                configurationSetName:
                  description: Optional provider configuration set override.
                  type: string
              required:
                - type
                - identity
            example:
              type: email
              identity: founder@example.com
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    type: boolean
                  identity:
                    type: string
                  type:
                    type: string
                    enum:
                      - domain
                      - email
                    description: >-
                      Identity scope. `domain` verifies via DNS (DKIM); `email`
                      verifies a single mailbox via a confirmation email.
                  identityType:
                    anyOf:
                      - type: string
                      - type: 'null'
                    description: Provider identity type, e.g. "DOMAIN" or "EMAIL_ADDRESS".
                  verifiedForSendingStatus:
                    type: boolean
                  messageId:
                    description: Verification email id (email identities only).
                    anyOf:
                      - type: string
                      - type: 'null'
                  dkimTokens:
                    type: array
                    items:
                      type: string
                    description: DKIM tokens for DNS records (domain identities).
                required:
                  - ok
                  - identity
                  - type
                  - identityType
                  - verifiedForSendingStatus
                  - dkimTokens
                additionalProperties: {}
              example:
                ok: true
                identity: example.com
                type: domain
                identityType: DOMAIN
                verifiedForSendingStatus: false
                dkimTokens:
                  - abc123token
                  - def456token
                  - ghi789token
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/InternalError'
      security:
        - DenchApiKey: []
        - AgentSession: []
components:
  responses:
    BadRequest:
      description: Invalid request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
    Unauthorized:
      description: Missing or invalid authentication
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
    NotFound:
      description: Operation or resource not found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
    InternalError:
      description: Server error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
  schemas:
    ApiError:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - message
            - type
            - code
          properties:
            message:
              type: string
            type:
              type: string
            code:
              type: string
            details: {}
  securitySchemes:
    DenchApiKey:
      type: http
      scheme: bearer
      bearerFormat: DENCH_API_KEY
      description: >-
        Workspace-scoped Dench API key from workspace settings. This is the same
        key used by DENCH_API_KEY in sandboxes.
    AgentSession:
      type: http
      scheme: bearer
      bearerFormat: dch_agent_*
      description: >-
        Agent session token created by `dench signin`. Gateway-backed routes
        exchange this token for the workspace gateway key.

````