---
schema_version: "1"
id: 7fb957275a7865be52f43af149412935aebfcdcd2bd171b648dad9dd8d2b6e8a
title: Connect REST API Limits
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/salesforce-app-limits-cheatsheet/guides/limits/salesforce-app-limits-chatter-rest.md
canonical_url: https://developer.salesforce.com/docs/platform/salesforce-app-limits-cheatsheet/guide/salesforce-app-limits-chatter-rest.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 4ae9e0259f42eb1cf197be1427a2e731e2acaea112bf1efd2c10571c1d855fed
products:
  - Salesforce Developer Limits and Allocations Quick Reference
  - Platform Developer Content
---

# Connect REST API Limits

Limits protect shared resources. These limits are for Connect REST API consumers.

Most Connect REST API requests are subject to the same rate limits as other Salesforce APIs. Only requests to Chatter REST API resources (a subset of Connect REST API resources) are subject to a per user, per application, per hour rate limit. When you exceed the rate limit, Connect REST API resources return a 503 Service Unavailable error code.

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.

**note:** Load, performance, and other system issues can prevent some limits from being reached. Limits can change without notice. Ensure that your applications make efficient use of available requests and gracefully handle the 503 error code.