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

# Verify an email address

> Checks whether an email address can receive mail, without writing to it. `status` is the verdict: `valid`; `invalid`, which also covers addresses never to be written to (spam traps, abuse and do-not-mail addresses); `risky`, when the domain accepts mail for every address, so this one cannot be confirmed; or `unknown`, when no verdict could be had.

A check takes a few seconds and ends within about 25 seconds. One that gets no verdict in time answers an empty `500` and costs nothing: try again. Verifications have their own limit, 60 a minute and 5,000 a day.

**Price:** \$0.01 a verdict; `unknown` is free. The price is held from your balance before the check runs, and released when it gives no verdict or is refused. **Scope:** enrichment, with a key that can write.



## OpenAPI

````yaml /openapi.json post /v1/emails/verify
openapi: 3.1.0
info:
  title: outbound.dev API
  version: v1
  description: Find people and companies, and see what every call costs, with one API key.
servers:
  - url: https://api.outbound.dev
security: []
tags:
  - name: People
    description: >-
      Search people with filters, a saved search or a plain-language query,
      count matches and look up filter values.
  - name: Companies
    description: >-
      Search companies, count matches, name one company by its name, domain or
      LinkedIn page, and list its people.
  - name: Saved searches
    description: Keep a search under a title and run it again, for people or for companies.
  - name: Lists
    description: >-
      Keep people or companies in lists: create and change lists, page through
      their rows, and add or remove people.
  - name: Folders
    description: Group lists of one kind into folders.
  - name: Enrichment
    description: >-
      Find people's work emails and phone numbers: one person, a batch of
      people, or a list.
  - name: Jobs
    description: >-
      Long tasks a call started: their progress, what they produced and what
      they were charged, and stopping them.
  - name: Accounts
    description: >-
      Connect the mailboxes and LinkedIn seats that campaigns and the inbox send
      from, and look after them.
  - name: Campaigns
    description: >-
      Email and LinkedIn campaigns: their steps, the people they enroll, their
      queue of messages, templates, the knowledge hubs and writing styles AI
      steps are written from, the tracking domain their links go through, and
      the lists every campaign leaves out.
  - name: Inbox
    description: >-
      Read and answer the conversations of your mailboxes and LinkedIn seats,
      and send new messages and invitations.
  - name: Account
    description: >-
      The calling key and its organization, its rate limits, and revoking the
      key.
  - name: Billing
    description: The balance, the ledger of every change to it, and the price list.
  - name: Usage and requests
    description: >-
      Calls and spend by day, and the record of every request of the last 30
      days.
paths:
  /v1/emails/verify:
    post:
      tags:
        - Enrichment
      summary: Verify an email address
      description: >-
        Checks whether an email address can receive mail, without writing to it.
        `status` is the verdict: `valid`; `invalid`, which also covers addresses
        never to be written to (spam traps, abuse and do-not-mail addresses);
        `risky`, when the domain accepts mail for every address, so this one
        cannot be confirmed; or `unknown`, when no verdict could be had.


        A check takes a few seconds and ends within about 25 seconds. One that
        gets no verdict in time answers an empty `500` and costs nothing: try
        again. Verifications have their own limit, 60 a minute and 5,000 a day.


        **Price:** \$0.01 a verdict; `unknown` is free. The price is held from
        your balance before the check runs, and released when it gives no
        verdict or is refused. **Scope:** enrichment, with a key that can write.
      operationId: postEmailsVerify
      parameters:
        - name: Idempotency-Key
          in: header
          required: false
          description: >-
            Names this operation, so a retry with the same key and body gets the
            first success again, marked `Idempotent-Replayed`, instead of
            running or charging twice. A mailbox's `password` is not compared:
            the same mailbox sent again with another password is the same call,
            and gets the first answer. Kept 24 hours for your organization and
            this route. A refusal (`4xx`) frees the key at once, so a corrected
            retry runs. After a server error (`5xx`), which may still take
            effect, the key stays held for 5 minutes from the call's start, and
            a retry in that time answers `409` `idempotency_in_progress`; after
            that, a send or import that may already have gone out answers `409`
            `idempotency_outcome_unknown` instead of running again. 1 to 255
            visible ASCII characters, such as a UUID.
          schema:
            type: string
            minLength: 1
            maxLength: 255
            pattern: ^[\x21-\x7E]+$
          example: 5f1c9d2e-8a4b-4e7c-9f30-6b2a1d8e4c75
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                email:
                  type: string
                  description: >-
                    The address to check, such as `ana.costa@fernway.co`. It is
                    checked trimmed and in lower case.
                  maxLength: 320
                  example: ana.costa@fernway.co
              required:
                - email
            example:
              email: ana.costa@fernway.co
      responses:
        '200':
          description: The address and its verdict.
          headers:
            X-Request-Id:
              $ref: '#/components/headers/RequestId'
            X-Charged-Usd:
              $ref: '#/components/headers/ChargedUsd'
            X-Balance-Usd:
              $ref: '#/components/headers/BalanceUsd'
            RateLimit-Limit:
              $ref: '#/components/headers/RateLimitLimit'
            RateLimit-Remaining:
              $ref: '#/components/headers/RateLimitRemaining'
            RateLimit-Reset:
              $ref: '#/components/headers/RateLimitReset'
            Idempotent-Replayed:
              $ref: '#/components/headers/IdempotentReplayed'
          content:
            application/json:
              schema:
                type: object
                required:
                  - email
                  - status
                properties:
                  email:
                    type: string
                    description: The address checked, trimmed and in lower case.
                  status:
                    type: string
                    enum:
                      - valid
                      - invalid
                      - risky
                      - unknown
                    description: >-
                      `valid`: it can receive mail. `invalid`: it cannot, or it
                      must never be written to (a spam trap, an abuse or
                      do-not-mail address). `risky`: its domain accepts mail for
                      every address, so this one cannot be confirmed. `unknown`:
                      no verdict could be had; it costs nothing.
              example:
                email: ana.costa@fernway.co
                status: valid
        '429':
          $ref: '#/components/responses/RateLimited'
        4XX:
          $ref: '#/components/responses/Error'
        5XX:
          $ref: '#/components/responses/ServerError'
      security:
        - apiKey: []
components:
  headers:
    RequestId:
      description: The request's id. Quote it when you write to support.
      schema:
        type: string
        example: req_6a1f0c2b9d4e8a7f3c5b2e10
    ChargedUsd:
      description: What this call cost, in US dollars as an exact six-decimal string.
      schema:
        type: string
        example: '0.005000'
    BalanceUsd:
      description: >-
        The organization's balance after this call, in US dollars as an exact
        six-decimal string.
      schema:
        type: string
        example: '9.995000'
    RateLimitLimit:
      description: >-
        The calls allowed in the window of the route's limit with the fewest
        calls left.
      schema:
        type: integer
        example: 20
    RateLimitRemaining:
      description: The calls left in that window.
      schema:
        type: integer
        example: 19
    RateLimitReset:
      description: Seconds until that window resets.
      schema:
        type: integer
        example: 42
    IdempotentReplayed:
      description: >-
        `true` on an answer given again for an `Idempotency-Key`: it is the
        first call's, and nothing ran or was charged this time. Absent
        otherwise.
      schema:
        type: string
        enum:
          - 'true'
    RetryAfter:
      description: Seconds to wait before calling again.
      schema:
        type: integer
        example: 42
  responses:
    RateLimited:
      description: >-
        Too many calls. Wait the seconds in Retry-After, then call again. When
        the limit reached does not say when it resets, such as a mail provider's
        own limit on a mailbox, Retry-After is 60. The RateLimit headers
        describe this API's own limits, so they come only with a 429 one of
        those gave. The body is empty.
      headers:
        Retry-After:
          $ref: '#/components/headers/RetryAfter'
        X-Request-Id:
          $ref: '#/components/headers/RequestId'
        RateLimit-Limit:
          $ref: '#/components/headers/RateLimitLimit'
        RateLimit-Remaining:
          $ref: '#/components/headers/RateLimitRemaining'
        RateLimit-Reset:
          $ref: '#/components/headers/RateLimitReset'
    Error:
      description: The request was refused. The body names the reason in `error.code`.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/RequestId'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    ServerError:
      description: >-
        Something failed on our side and nothing was charged. Retry with
        backoff; quote X-Request-Id if it persists. The body is empty.
      headers:
        X-Request-Id:
          $ref: '#/components/headers/RequestId'
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
            - doc_url
          properties:
            code:
              type: string
              description: >-
                Stable and machine-readable: branch on it. It never changes
                meaning.
            message:
              type: string
              description: >-
                A human-readable explanation for logs. It may be reworded at any
                time.
            param:
              type: string
              description: The request field the error is about, when there is one.
            doc_url:
              type: string
              description: The code's entry in the errors reference.
            request_id:
              type: string
              description: >-
                The request's id, as in the X-Request-Id header. Quote it to
                support.
      example:
        error:
          code: insufficient_balance
          message: Your balance cannot cover this call. Add funds and try again.
          doc_url: https://docs.outbound.dev/errors#insufficient_balance
          request_id: req_6a1f0c2b9d4e8a7f3c5b2e10
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: >-
        An API key from the console, starting `ob_live_`, sent as
        `Authorization: Bearer <key>`.

````

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