UserGems · Rate Limits

Usergems Rate Limits

UserGems publishes one hard API rate limit — 20 requests per second, one record per request — in the Help Center article "Using the UserGems API". It is not in the Developer Hub reference, which lists only the 429 status code. Because there is no bulk endpoint, that limit is also the ceiling on ingestion throughput: 20 records/second is the maximum rate at which any first-party system can push contacts or accounts into UserGems. Separately, UserGems enforces a downstream Salesforce-side quota of 20,000 API calls per Salesforce instance per 24-hour rolling window across all UserGems products, with sync continuing the following day if reached. Custom caps above or below 20K are negotiable through a Customer Success Manager. Maximum platform throughput is approximately 1,000 job changes per day per customer. The runtime signal is the gap: UserGems documents no X-RateLimit-*/RateLimit-* response headers and no Retry-After, so a client that hits 429 has no published way to learn its remaining budget or its reset time and must back off blindly.

Usergems Rate Limits is the machine-readable rate-limit profile for UserGems on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring salesforce-api-calls-per-job-change, salesforce-api-calls-per-contact, and job-changes-per-day.

The profile also includes response codes documented for throttled and quotaExceeded.

Tagged areas include Rate Limiting, Quotas, and Salesforce.

5 Limits Throttle: 429 Quota: 429
Rate LimitingQuotasSalesforce

Limits

api-key
salesforce-instance
contact-tracking
salesforce-api-calls-per-job-change
account-tracking
salesforce-api-calls-per-contact
throughput
job-changes-per-day

Sources