Rate Limits

The Sayari API uses a tiered rate limiting system to ensure reliable access and maintain performance across all endpoints.

Sayari reserves the right to adjust rate limits to maintain platform stability during surges in activity.

At a Glance

Tier	Requests	Window	Block Duration	Avg. Requests/sec
Standard	200	1 minute	1 minute	~3.33
Advanced	15	10 seconds	10 seconds	~1.5

Tier 1: Standard Endpoints

200 requests per minute — exceeding this limit results in a 1-minute block.

Most endpoints fall under the standard tier, including but not limited to:

/v1/resolution
/v1/entity
/v1/entity_summary
/v1/record
/v1/sources
/v1/projects
/v1/notifications
/v1/attribute
/v1/resource

Tier 2: Advanced Endpoints

15 requests per 10 seconds — exceeding this limit results in a 10-second block.

These endpoints have stricter limits due to their computational complexity:

/v1/search
/v1/traversal
/v1/ubo
/v1/downstream
/v1/watchlist
/v1/shortest_path
/v1/supply_chain/upstream

Handling Rate Limit Errors

When a rate limit is exceeded, the API returns a 429 status code:

1 {
2   "status": 429,
3   "success": false,
4   "messages": ["Too many requests within too short of a period."]
5 }

What happens if the limit is exceeded?

A temporary block is enforced on the affected endpoint(s). For standard endpoints, the block lasts 1 minute. For advanced endpoints, the block lasts 10 seconds.

Can I increase the rate limit maximums?

If you’re consistently hitting rate limits, reach out to your Account Manager to discuss your needs.

How do I know which tier an endpoint belongs to?

Advanced endpoints are explicitly listed in the Tier 2 section above. If an endpoint is not listed there, it falls under the standard tier. Contact support if you’re unsure about a specific endpoint.

1	{
2	"status": 429,
3	"success": false,
4	"messages": ["Too many requests within too short of a period."]
5	}