Sugarcrm Rate Limits

Published throughput limits for the Sugar REST API on SugarCloud, taken from the SugarCloud Policy Guide. Sugar enforces limits at the platform/instance level rather than per API key, and states them as policy prose - it does NOT document any RateLimit-* / X-RateLimit-* response headers or a documented 429 contract. Traffic in excess of the published rate is handled by temporary IP blocking, so a client sees a connection-level failure rather than a structured throttle response. On-site (self-hosted) deployments are governed by the customer's own infrastructure, not by this policy.