Connect REST API Limits

Rate Limits

For migrated orgs and orgs created in Summer ’24 and later, only requests to Chatter REST API resources are subject to the per user, per application, per hour rate limit. The documentation for every Chatter resource specifies that Chatter is required. Requests to resources that don’t require Chatter count toward the Salesforce Platform total API request allocations, which are per org and span a 24-hour period.

For applications using a session ID from Salesforce, the rate limit is per user, per hour—there isn’t a separate bucket for applications. All applications the user accesses with a session ID use this general quota. To take advantage of the per user, per application, per hour limit, use OAuth tokens.

To build apps that don’t hit the rate limit, use these guidelines.

• If you hit limits when running tests, use multiple users to simulate a real-world scenario.
• When polling for feed updates, don’t exceed 1 poll per minute (60 polls per hour). To return more results in one request, increase the page size.
• When polling for private messages, don’t exceed 60 polls per hour.
• To avoid making multiple requests, cache metered static assets such as file and dashboard renditions (group and user profile pictures are not metered).
• Set up two connected apps: one for automated testing and one for manual testing and development. Don’t share connected apps with other developers.
• Use a unique connected app for the production environment.
• Don’t share connected apps between applications.

Salesforce Platform REST API rate limits and query language work better for these use cases.

• Migrate or synchronize user profiles between systems.
• Create analytic applications.
• Write queries that return records and fields.

Integer Limits

Connect REST API supports most 64-bit integers. Integers greater than 2³¹-1 and less than 10¹⁸ must be in quotes. Integers larger than 10¹⁸ aren’t supported.