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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/mailfloss:mailfloss-privacy-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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
openapi: 3.2.0
info:
title: mailfloss Privacy API
version: 1.0.0
description: 'mailfloss email verification API — version 1.
## Authentication
Every request must include your API key as a Bearer token in the `Authorization` header:
```
Authorization: Bearer YOUR_API_KEY
```
This is the only accepted authentication scheme for v1. The legacy `?api_key=` query parameter is **not** accepted on v1 endpoints.
## Conventions
List endpoints return a `{ data, pagination }` envelope. Errors return a stable machine-readable `code` (branch on it, not the message). Timestamps are ISO 8601 UTC.'
contact:
name: mailfloss support
url: https://mailfloss.com
email: support@mailfloss.com
servers:
- url: https://api.mailfloss.com
description: Production
tags:
- name: Privacy
description: Data privacy / erasure API
paths:
/v1/erasures:
post:
summary: Erase stored verification records (data privacy)
description: Data-privacy erasure API — permanently removes stored verification records, bounce and complaint history and the private scoring log for the supplied email addresses, and blocks later bounce or complaint imports for them. (Renamed from /v1/delete for clarity.) See https://developers.mailfloss.com for the public docs.
tags:
- Privacy
security:
- apiKeyHeader: []
parameters:
- schema:
type: string
minLength: 1
maxLength: 255
description: 'Optional Stripe-style idempotency key. POST requests carrying this header are deduplicated for 24 hours: a retry with the same key returns the cached response (with header `Idempotent-Replayed: true`) instead of re-running the handler. Different request body with the same key returns 422 (fingerprint mismatch). Concurrent retries while the first is still in flight return 409 (in progress).'
required: false
description: 'Optional Stripe-style idempotency key. POST requests carrying this header are deduplicated for 24 hours: a retry with the same key returns the cached response (with header `Idempotent-Replayed: true`) instead of re-running the handler. Different request body with the same key returns 422 (fingerprint mismatch). Concurrent retries while the first is still in flight return 409 (in progress).'
name: Idempotency-Key
in: header
requestBody:
content:
application/json:
schema:
type: object
properties:
emails:
type: array
items:
type: string
responses:
'200':
description: Delete acknowledgement
content:
application/json:
schema:
type: object
properties:
status:
type: string
enum:
- success
description: 'Always `"success"` when the erasure request was accepted and processed. Erasure is idempotent: addresses that were not present are a no-op that still returns `"success"`.'
required:
- status
example:
status: success
'400':
description: Invalid request — a query or body parameter failed validation. Branch on `code`, not the message.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
example:
error:
code: invalid_request
message: A required parameter is missing or malformed.
type: invalid_request_error
request_id: req_1a2b3c4d5e6f
'401':
description: Authentication failed — the API key is missing, malformed, unknown, expired, or revoked. (Expired/revoked/unknown are intentionally indistinguishable.)
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
example:
error:
code: invalid_api_key
message: Invalid API key.
type: authentication_error
request_id: req_1a2b3c4d5e6f
'403':
description: Forbidden — the API key lacks the required scope, or the account is restricted (suspended / paused / banned).
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
example:
error:
code: forbidden_scope
message: API key does not have the required scope.
type: authentication_error
request_id: req_1a2b3c4d5e6f
'409':
description: Idempotency-Key reuse while an earlier request with the same key is still in progress.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
example:
error:
code: idempotency_in_progress
message: A request with this Idempotency-Key is still being processed. Retry shortly.
type: conflict_error
request_id: req_1a2b3c4d5e6f
'422':
description: Idempotency-Key was previously used with a different request body (fingerprint mismatch).
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
example:
error:
code: idempotency_key_reused
message: This Idempotency-Key was already used with a different request body.
type: invalid_request_error
request_id: req_1a2b3c4d5e6f
'429':
description: Rate limited — too many requests. Honor the Retry-After / X-RateLimit-* response headers.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
example:
error:
code: rate_limited
message: Rate limit exceeded. Retry after the period indicated by the Retry-After header.
type: rate_limit_error
request_id: req_1a2b3c4d5e6f
'500':
description: Unexpected server error or timeout.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
example:
error:
code: server_error
message: An unexpected error occurred. Please retry.
type: api_error
request_id: req_1a2b3c4d5e6f
'503':
description: Service temporarily unavailable, or an upstream dependency could not be reached.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorEnvelope'
example:
error:
code: service_unavailable
message: The service is temporarily unavailable. Please retry shortly.
type: api_error
request_id: req_1a2b3c4d5e6f
operationId: postV1Erasures
x-operation-id-source: derived
components:
schemas:
ErrorEnvelope:
type: object
properties:
error:
type: object
properties:
code:
type: string
description: Stable machine-readable error code. See docs/api/v1_contract.md for the frozen enum.
message:
type: string
description: Human-readable error message. Do NOT pattern-match — use code instead.
type:
type: string
description: Coarse category derived from HTTP status (authentication_error, billing_error, invalid_request_error, rate_limit_error, not_found_error, conflict_error, api_error).
request_id:
type:
- string
- 'null'
description: Echoes the X-Request-Id response header.
required:
- code
- message
- type
- request_id
required:
- error
securitySchemes:
apiKeyHeader:
type: http
scheme: bearer
description: 'Send your API key as a Bearer token: `Authorization: Bearer <token>`. This is the only accepted authentication scheme for the v1 API.'