HoneyBook · Rate Limits

Honeybook Rate Limits

HoneyBook publishes no rate-limit documentation because it publishes no public API reference at all. Third-party integration guides describing hypothetical HoneyBook API usage mention a generic HTTP 429 "too many requests" response and recommend exponential backoff, but do not cite a specific numeric threshold (requests per minute/hour) and are not independently verifiable against a live HoneyBook reference. The only concretely documented "limits" in the HoneyBook ecosystem are product feature caps enforced by membership plan (e.g. Starter capped at 2 live lead forms and 1 scheduler session type; Essentials capped at 10 lead forms and 2 team members) rather than API request-rate limits.

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

It captures 5 rate-limit definitions, measuring requests, forms, session_types, and seats.

The profile also includes 1 backoff/retry policy defined and response codes documented for throttled.

Tagged areas include CRM, Clientflow, Rate Limiting, and Quotas.

5 Limits Throttle: 429
CRMClientflowRate LimitingQuotas

Limits

Public API Request Rate account
requests
not published (no public API exists)
HoneyBook has never published a self-serve API reference or a rate-limit policy.
Starter Live Lead Forms account
forms
2
Product feature cap, not an API rate limit.
Starter Scheduler Session Types account
session_types
1
Product feature cap, not an API rate limit.
Essentials Live Lead Forms account
forms
10
Product feature cap, not an API rate limit.
Essentials Team Members account
seats
2
Product feature cap, not an API rate limit.

Policies

Backoff Strategy (Modeled)
Third-party integration guides suggest exponential backoff on HTTP 429 for any hypothetical HoneyBook API call, mirroring generic REST API best practice rather than a HoneyBook-published policy.

Sources