Dyspatch · Rate Limits
Dyspatch Rate Limits
Dyspatch Rate Limits is the rate-limit profile for Dyspatch on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the X-RateLimit-Remaining response header.
Tagged areas include Company, Email, Email Templates, Marketing, and Messaging.
0 Limits
X-RateLimit-Remaining
Transcribed from the provider's documentation on 2026-08-13 — ['docs.dyspatch.io/api/', 'openapi/_original/dyspatch-ope....
View Source
Limits
Dyspatch publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Dyspatch publishes NO numeric rate limit — not a requests-per-second ceiling, not a per-plan quota, not a burst allowance. What it does publish is the runtime signal, and it publishes it well: every single response definition in the OpenAPI (success and error alike) declares an X-RateLimit-Remaining response header, and a dedicated 429 "Rate limit exceeded" response is wired onto every operation in the spec. An agent can therefore always see how much budget is left and can always detect exhaustion; it just cannot know the ceiling in advance. limit_count is an honest 0: the headers are documented, the numbers are not.
CompanyEmailEmail TemplatesMarketingMessagingSMSPush NotificationsLocalizationContent ManagementDeveloper Tools
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.