Inboxkit API Documentation#
Introduction#
Welcome to Inboxkit, the most powerful platform for automating your cold email infrastructure at scale. Orchestrating campaigns across thousands of mailboxes on hundreds of domain, Inboxkit streamlines the entire process through intelligent automation.Our platform seamlessly integrates with Google Workspace and Microsoft 365, allowing you to:Automatically provision and configure unlimited domains and mailboxes
Scale your cold email operations without manual setup overhead
Maintain pristine sender reputation across your entire infrastructure
Monitor deliverability and performance in real-time
Getting Started#
Authentication & API Access#
Your journey begins with obtaining your unique API credentials. These keys authenticate all requests and ensure secure access to your Inboxkit resources.1.
Log into your Inboxkit/InboxAutomate Dashboard
2.
Navigate to Settings → API & Integrations
3.
Click Generate API Key or copy your existing key
4.
Store your key securely: it provides full access to your account
Base URL#
All API requests should be directed to our primary endpoint:https://api.inboxkit.com/v1
Rate Limits & Fair Usage#
To ensure optimal performance for all users, we enforce the following limits:| Operation | Rate Limit |
|---|
| Standard API calls | 5,000 requests/minute per IP address |
| Domain search & availability checks | 50 requests/minute, 1,000 requests/hour |
| Bulk mailbox provisioning | 10 requests/minute |
| Inbox placement tests | 20 requests/minute |
| Reputation monitoring (InfraGuard) | 30 requests/minute |
| Cloudflare domain connect | 10 requests per 5 minutes |
Every response includes RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and RateLimit-Policy headers for the standard limit. RateLimit-Reset is the number of seconds until the window resets.
When you go over the standard limit, you get 429 Too Many Requests with a Retry-After header in seconds and this body:
{
"message": "Too many requests, please try again later."
}
Wait for Retry-After, then retry. Use exponential backoff if you get 429 again.
Endpoints that read a mailbox can also return 429 when the mailbox provider is limiting that mailbox. Those responses have a code field and may include Retry-After. Handle them the same way.
Consider batching operations to maximize efficiency
What's Next?#
Ready to start building? Here's your roadmap:Webhooks: Real-time notifications for critical events Changelog (in the sidebar): Changes to the API that may affect your integration
Modified at 2026-11-11 09:37:05
