DeBounce Reverse API

The Reverse API from DeBounce — 1 operation(s) for reverse.

Operations 1

GET /v1/reverse/ Reverse email lookup #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/debounce-reverse-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

debounce-reverse-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: DeBounce Email Validation Reverse API
  description: Single email validation, reverse lookup, balance, and usage endpoints.
  license:
    name: MIT
  version: 1.0.0
servers:
- url: https://api.debounce.io
security:
- ApiKeyQuery: []
tags:
- name: Reverse
paths:
  /v1/reverse/:
    get:
      summary: Reverse email lookup
      description: Reverse email lookup to find additional data associated with an email address
      operationId: reverseEmailLookup
      parameters:
      - name: api
        in: query
        description: Your DeBounce API key
        required: true
        schema:
          type: string
      - name: email
        in: query
        description: The email address to lookup
        required: true
        schema:
          type: string
          format: email
      responses:
        '200':
          description: Reverse lookup completed successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReverseResult'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Unauthorized - Invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      tags:
      - Reverse
components:
  schemas:
    ReverseResult:
      type: object
      required:
      - success
      properties:
        email:
          description: The email address that was looked up
          type: string
          format: email
        data:
          description: Additional data found for the email address
          type: object
          additionalProperties: true
        success:
          description: Whether the lookup was successful
          type: integer
          enum:
          - 0
          - 1
    Error:
      type: object
      required:
      - error
      properties:
        error:
          type: string
        message:
          type: string
        debounce:
          type: object
          properties:
            error:
              type: string
            code:
              type: string
        success:
          type: string
          enum:
          - '0'
  securitySchemes:
    ApiKeyQuery:
      type: apiKey
      in: query
      name: api
      description: API key for authentication