Ortto · Rate Limits

Ortto Rate Limits

Ortto publishes a dedicated rate-limit reference. The request-rate ceiling is tied to the subscription plan — 10 requests per second on Professional and 30 requests per second on Business and Enterprise (negotiable) — layered on top of a per-IP ceiling of 2,000 requests per 10 seconds and 6,000 per 60 seconds. A separate bad-request limiter bans an IP for 15 seconds after 15 malformed or 15 failed-credential requests in a 15-second window. Payload caps apply independently: 100 contacts or 100 activities per request, 2 MB per payload, 16 kB per individual activity, and 50 events per custom activity per contact per 24 hours. On exhaustion the API returns 429 with a JSON body carrying the error code "rate-limit" and a try-in-seconds field; Ortto returns no X-RateLimit-* or RateLimit-* response headers, so a client's only runtime signal is the body of the 429 itself.

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

It captures 14 rate-limit definitions, measuring requests, bad_requests, failed_auth_requests, records, and bytes.

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

Tagged areas include Marketing Automation, CDP, Customer Data Platform, Analytics, and Email.

14 Limits Throttle: 429
Marketing AutomationCDPCustomer Data PlatformAnalyticsEmailRate LimitingQuotasThrottling

Limits

Professional Plan Request Rate account
requests
10
10 requests per second on the Professional plan.
Business Plan Request Rate account
requests
30
30 requests per second on the Business plan.
Enterprise Plan Request Rate account
requests
30
30 requests per second, negotiable upon request.
IP Request Rate (10s) ip
requests
2000
IP Request Rate (60s) ip
requests
6000
Bad Request Limiter ip
bad_requests
15
15 malformed requests in 15 seconds triggers a 15-second IP ban.
Failed Credential Limiter ip
failed_auth_requests
15
15 failed-credential requests in 15 seconds triggers a 15-second IP ban.
People Per Merge Request request
records
100
Up to 100 people per /person/merge call.
Activities Per Create Request request
records
100
Up to 100 activity events per /activities/create call.
Payload Size request
bytes
2097152
2 MB maximum total payload size.
Individual Activity Size request
bytes
16384
16 kB maximum per individual activity.
Custom Activity Events Per Contact contact
events
50
50 events per custom activity per contact per 24 hours.
Activity Backdating Window request
days
90
Activities may be backdated up to 90 days or the configured data-retention period.
Transactional Email Attachments request
attachments
5
Up to 5 base64-encoded attachments per transactional email.

Policies

Regional Endpoints
Use the AU or EU service endpoints for accounts whose instance region is set accordingly; limits are enforced per instance.
Async Processing
Set async true on large merge batches so Ortto queues processing instead of handling it inline.
Backoff Strategy
Clients should back off for the number of seconds returned in the try-in-seconds field of the 429 body, with jitter. There is no Retry-After header to honor.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/ortto-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.