Menu Authentication

Get started

Authentication

One API key, sent as a Bearer token with every request. The same key signs in the SDKs and the MCP server.

Create a key

Sign in and open Settings → API keys. A key comes with any account, on the free plan too. The full token starts with fep_ and is shown once, when you create it; after that the page shows only its first characters. Lost it – revoke it and create a new one.

All your keys draw on one budget – the quota and the per-minute limit are counted per user, not per key – so a key per project or per CI is about revoking one without touching the others, not about more requests.

Send it with every request

Every endpoint expects the key in the Authorization header:

Header
Authorization: Bearer fep_...

The samples, the SDKs and the MCP snippets read it from the FAKE_EMAIL_API_KEY environment variable. A missing, unknown, revoked or expired key answers 401 unauthorized; a plan without API access answers 403 plan_forbidden (Errors).

Server-side only

Treat the key like a password. This is a server-to-server API: CORS is off on api.fake-email.pro and no browser origin is allowed, so a fetch straight from a web page will not reach it. That is deliberate – it is also the only thing standing between a key in a bundle and anyone who opens devtools. Call the API from your backend, your test runner or CI.

In CI

Store the key as a secret named FAKE_EMAIL_API_KEY and expose it to the job as an environment variable. The SDKs pick it up with no code; for an agent in CI, the MCP guide has the .mcp.json that reads the same variable.

GitHub Actions
# .github/workflows/e2e.yml
jobs:
  e2e:
    runs-on: ubuntu-latest
    env:
      FAKE_EMAIL_API_KEY: ${{ secrets.FAKE_EMAIL_API_KEY }}
    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - run: npx playwright test
Something missing, confusing or wrong on this page? Tell us