Kit · Rate Limits
Convertkit Rate Limits
Rate limits enforced by the Kit (formerly ConvertKit) REST API v4.
Convertkit Rate Limits is the machine-readable rate-limit profile for Kit on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions.
Limit state is signalled in the documented, x_ratelimit, ratelimit, and retry_after response headers.
Tagged areas include Email Marketing, Creator Economy, Subscribers, Automation, and Newsletters.
3 Limits
documentedx_ratelimitratelimitretry_after
Transcribed from the provider's documentation on 2026-08-13 — developers.kit.com/api-reference/response-codes.
View Source
Email MarketingCreator EconomySubscribersAutomationNewslettersSequencesFormsBroadcastWebhookMCPAgentsAuthenticationMarketing AutomationLanding PagesSegmentationEmail CampaignsSoftware-as-a-ServiceCommerceA2AEmail
Limits
API Key: 120 requests per 60 seconds per API key
Suitable for personal account automation and simple integrations.Some endpoints (bulk operations, purchase creation) require OAuth exclusively.
OAuth 2.0: 600 requests per 60 seconds per OAuth access token
Required for apps distributed through the Kit App Store.Supports Authorization Code Grant flow.Web servers use the refresh token flow.SPAs and mobile apps use PKCE flow.Recommended for public integrations needing higher throughput.
OAuth 2.0 (Kit MCP): 120 requests per 60 seconds per token
The Kit MCP server is rate-limited to 120 req/min per token — one fifth of the 600/60s an OAuth token gets against the REST API directly.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.