Ortto · Rate Limits

Ortto Rate Limits

The Ortto API enforces per-request payload limits and per-resource throttles rather than a single global RPM. People merge and activity create accept up to 100 records per request; activity payloads are capped at 2 MB. Custom activity events are limited to 50 events per activity per contact per 24 hours, and activities can be backdated up to 90 days (or the configured data retention period). Account-level request-rate limits are applied by Ortto but specific per-endpoint RPM/RPS values are not publicly reconciled in this artifact.

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 7 rate-limit definitions, measuring records, bytes, events, days, and attachments.

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.

7 Limits Throttle: 429
Marketing AutomationCDPCustomer Data PlatformAnalyticsEmailRate LimitingQuotasThrottling

Limits

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.
Activity Payload Size request
bytes
2097152
2 MB maximum payload for /activities/create.
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 retention period.
Transactional Email Attachments request
attachments
5
Up to 5 base64-encoded attachments per transactional email.
Account Request Rate account
requests
see provider documentation
Per-account request-rate throttling applies; specific values not publicly reconciled.

Policies

Regional Endpoints
Use the AU or EU service endpoints for accounts whose instance region is set accordingly.
Async Processing
Set async true on large merge batches so Ortto queues processing instead of handling inline.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources