To use the EmailKit API, you need an API key. API keys authenticate your requests and link usage to your account's credit balance.
Sign in to your EmailKit dashboard
Click API Keys in the sidebar
Click Create API Key
Enter a name for the key (e.g., "Production", "My App", "Testing")
Optionally set an expiration (days) or leave blank for no expiration
Optionally check Test key to create a key for testing (test keys don't consume credits)
Click Create
Copy the key immediately — it starts with ek_ and is only displayed once
Important: Store your API key securely. You won't be able to view it again after creation. If you lose it, you'll need to create a new one.
Include the key in the Authorization header of every API request:
Authorization: Bearer ek_live_abc123def456...Example with curl:
curl -X POST https://api.emailkit.dev/api/v1/verify \
-H "Authorization: Bearer ek_live_abc123def456..." \
-H "Content-Type: application/json" \
-d '{"email": "check@example.com"}'From the API Keys page, you can:
View all keys — See the name, creation date, last used date, and status of each key
Revoke a key — Click the delete button next to a key to permanently revoke it. This action is irreversible.
Use separate keys for different environments — Create one key for development/testing and another for production
Never expose keys in client-side code — API keys should only be used in server-side code, never in browser JavaScript or mobile apps
Rotate keys periodically — Create a new key, update your application, then revoke the old key
Set expiration dates — For temporary integrations or contractor access, set keys to auto-expire
Use test keys during development — Test keys let you test your integration without consuming credits
All EmailKit API keys start with ek_ followed by additional identifiers:
ek_live_... — Live production key (consumes credits)
ek_test_... — Test key (does not consume credits, returns mock results)
If you suspect a key has been compromised:
Go to API Keys in the sidebar
Find the compromised key
Click the delete/revoke button
Create a new key immediately
Update your application with the new key
Revoking a key is instant — all requests using that key will start failing immediately with a 401 Unauthorized error.