Deadsimple Email · Authentication Profile

Deadsimple Email Authentication

Authentication

Dead Simple Email supports two authentication methods: API keys and OAuth 2.1 tokens, both sent as Bearer tokens in the Authorization header.

Deadsimple Email declares 2 security scheme(s) across its OpenAPI definitions.

EmailArtificial IntelligenceAutomationCommunications
Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

API Key http-bearer
MCP OAuth oauth2
· flows: ,

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-05'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://deadsimple.email/blog/mcp-oauth-ai-agents-email.html
sources:
- https://deadsimple.email/blog/mcp-oauth-ai-agents-email.html
- https://deadsimple.email/blog/getting-started.html
- https://deadsimple.email/blog/automate-customer-onboarding-ai-email.html
description: 'Dead Simple Email supports two authentication methods: API keys and OAuth 2.1 tokens, both sent as Bearer tokens in the Authorization
  header.'
schemes:
- type: http-bearer
  name: API Key
  evidence: Keys and OAuth coexist on one endpoint. Dead Simple's server at https://api.deadsimple.email/mcp accepts dse_ API keys and dse_oat_
    OAuth tokens interchangeably across the same 19-tool surface.
  location: header
  header: Authorization
  how_to_obtain: Create an API key under Settings → API Keys; it starts with dse_ and is provided once.
- type: oauth2
  name: MCP OAuth
  evidence: MCP standardized authorization on OAuth 2.1. The optional layer for HTTP transports arrived in the March 2025 spec revision, letting
    a client authenticate against a server it has never seen without pre-registration.
  location: header
  header: Authorization
  flows:
  - authorization_code
  - refresh_token
  token_url: '.../oauth/token'
  authorize_url: '.../oauth/authorize'
  scopes:
  - email
  how_to_obtain: Dynamic client registration at the registration_endpoint returns a client_id; the user authorizes via the authorization_endpoint
    and the client exchanges the code at the token_endpoint to receive a dse_oat_ access token.
docs: https://deadsimple.email/blog/mcp-oauth-ai-agents-email.html

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact 
curl "https://apis.io/api/v1/security/deadsimple-email-authentication"
All security posture 
curl "https://apis.io/api/v1/security?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.

GitHub Google LinkedIn

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