SendHub · Rate Limits
Sendhub Rate Limits
Sendhub Rate Limits is the rate-limit profile for SendHub 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 request, response, documented, and note response headers.
Tagged areas include Company, SMS, Messaging, Text Messaging, and Communications.
0 Limits
requestresponsedocumentednote
Transcribed from the provider's documentation on 2026-08-13 — integrations.sendhub.com/SendHub-API-v1-Documentation.html.
View Source
Limits
SendHub publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
SendHub documents rate limiting behaviourally but publishes NO numeric limit: the v1 reference defines a 429 "You've sent too many requests in a short amount of time and are being rate-limited" response and a 420 "You've reached your plan's API limit for this month or you're on a plan that doesn't include API access" response on every operation, but never states a requests-per-second/minute ceiling or a monthly API call allowance. The monthly allowance implied by 420 is a plan attribute that does not appear on the published pricing page either (see plans/sendhub-plans-pricing.yml). No RateLimit-* / X-RateLimit-* / Retry-After response headers are documented, and none were observed on a live unauthenticated request to https://api.sendhub.com/v1/contacts (HTTP 401, probed 2026-08-13). Retry timing is carried in the RESPONSE BODY, not a header, which means a generic HTTP client cannot back off correctly without parsing SendHub's error envelope.
CompanySMSMessagingText MessagingCommunicationsMarketingWebhookVoIP
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.