EmailGuard
  • Pricing
Log inRegister
DocumentationAPI ReferenceKnowledge Base

Documentation

Documentation

Help center guides

Getting started
  • Introduction
  • Getting started in the app
  • Sign-in and account recovery
Teams
  • Creating and switching teams
  • Team settings
  • Inviting and managing members
  • Accepting team invitations
  • Understanding roles
Account
  • Managing your account
  • Securing your account
Billing
  • Billing plans and subscription
  • Billing usage
Notifications
  • Notification rules
  • Notification channels
Security
  • Audit log
Developers
  • Creating API keys
  • Your first email detection check
  • Integrating from the dashboard

Creating API keys

How team admins create, scope, and rotate API keys for programmatic access.

On this page

  • Before you create a key
  • Create the key
  • Rotate or revoke
  • Related articles

Team owners and admins can create API keys from Team → API keys.

Before you create a key

  1. Decide which endpoints your integration needs — each route requires specific API key scopes.
  2. Prefer the minimum scopes required. You can always create a new key with broader access later. Public API routes are scoped to the team that owns the key.

Create the key

  1. Open Team → API keys.
  2. Choose Create key.
  3. Name the key for the integration (for example CI deploy or Signup detect).
  4. Select the scopes your app needs (include email:detect for classification).
  5. Copy the secret immediately — it is shown only once.

Keys use the gsk_live_ prefix in production. Send them as Authorization: Bearer … or X-API-Key: … on every request.

Rotate or revoke

If a secret is exposed, revoke the key from Team settings and issue a replacement. Update your integration before deleting the old key to avoid downtime.

Related articles

  • Your first email detection check
  • API key scopes
  • Team roles and permissions
  • Integrating from the dashboard