Evercontact Rate Limits
Evercontact publishes NO HTTP rate limits for its REST API. The API page describes the endpoints only as "idempotent, versioned, rate-limit friendly" and names no numeric limit, window, burst allowance, 429 behaviour or response-header family. What IS published is a per-account daily PROCESSING QUOTA attached to each subscription tier - the number of conversational emails the platform will analyze per day - which is a product quota on the ingestion pipeline, not a limit on API calls. Those quotas are recorded below and clearly labelled as such; they must not be read as API request limits. An integrator cannot currently determine, from anything Evercontact publishes, how many API requests per second/minute/day they may make or what an exhausted limit returns.
Evercontact Rate Limits is the machine-readable rate-limit profile for Evercontact on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring conversational_emails_analyzed.
Limit state is signalled in the documented, rate_limit_family, retry_after, and request_id response headers.
The profile also includes response codes documented for throttled and note.
Tagged areas include Rate Limiting and Contact Data.
documentedrate_limit_familyretry_afterrequest_id
Limits
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.