Last updated Sep 9, 2025

Rate limits

This page documents the key rate limits that apply when using the Teamwork Graph connector SDK. Understanding these limits helps you design robust connectors that avoid throttling.

Rate limits are enforced per app and tenant combination.

Operation	Limit
`setObject`	100 objects per request 1,500 objects per minute, or 50,000 objects per minute if `operationType=BACKFILL`
`getObjectByExternalId`	1 `externalId` per request 1,500 objects per minute
`deleteObjectsByProperties`	1 `property` per request 1,500 requests per minute
`deleteObjectsByExternalId`	100 `externalIds` per request 500 `externalIds` per minute
`setUsers`	100 users per request 5,000 users per minute
`getUserByExternalId`	1 `externalId` per request 10,000 `externalIds` per minute
`deleteUsersByExternalId`	100 `externalIds` per request 1,000 `externalIds` per minute
`mapUsers`	100 mappings per request 5,000 mappings per minute
`setGroups`	100 groups per request 1,000 groups per minute
`getGroupByExternalId`	1 `externalId` per request 1,000 `externalId` per minute
`deleteGroupsByExternalId`	100 `externalIds` per request 1,000 `externalIds` per minute

Additional notes

Batching: The ingesting objects limit is based on the total number of entities ingested per minute, regardless of how many requests are made. For example, if you send a batch request with 100 entities, that counts as 100 towards the limit.
Backfill: The higher limit for backfill operations is intended for non-real-time, bulk ingestion scenarios.
Deletes: Only deletes by key are rate-limited. Other delete operations are bulk and processed over time and thus don’t have a rate limit applied.