SleekFlow · Rate Limits

Sleekflow Rate Limits

SleekFlow enforces a per-account API call usage limit on the Platform API that is determined by the account's subscription plan and is shared across the Platform API, Make.com, and Zapier integration requests. Platform API access itself requires a Premium or Enterprise plan. Specific per-minute / per-day request quotas are not published and are not reconciled in this artifact. WhatsApp Business / channel messaging is additionally subject to the underlying provider's (Meta and other channels') messaging limits and quality-based throughput tiers.

Sleekflow Rate Limits is the machine-readable rate-limit profile for SleekFlow on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and conversations.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Messaging, Omnichannel, WhatsApp, Customer Engagement, and Social Commerce.

3 Limits Throttle: 429
MessagingOmnichannelWhatsAppCustomer EngagementSocial CommerceRate LimitingQuotasThrottling

Limits

Platform API Calls account
requests
see provider documentation
Per-account API call allowance set by subscription plan; shared across Platform API, Make.com, and Zapier requests.
Make.com / Zapier Integration Calls account
requests
shared with Platform API quota
Counts against the same per-account API call allowance.
WhatsApp Business Messaging account
conversations
governed by Meta WhatsApp Business limits
Throughput and template messaging governed by Meta's quality-based messaging tiers, not by SleekFlow directly.

Policies

Plan-Gated Access
Platform API access requires a Premium or Enterprise subscription.
Shared Quota
Platform API, Make.com, and Zapier requests draw from a single shared per-account API call allowance.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.

Sources