- Usage Example
- Leading Practices
- Managing Items and Permissions
- Managing Security Identities in a Security Identity Provider
- Updating the Status of a Push Source
- Resetting a Push Source
- Creating a File Container
- Understanding the orderingId Parameter
- Understanding the API Processing Delay
- Troubleshooting API Error Codes
- API Reference
Push API Limits
The Push API enforces certain request size and call frequency limits.
These limits could change at any time without prior notice.
Request Size Limits
You will typically get a
413 Request Entity Too Large response if your total Push API request size exceeds:
- 256 MB when pushing a large file container. See:
- 6 MB when pushing a single item or security identity.
- Adding or Updating a Single Item in a Push Source
- Adding or Updating a Single Security Identity
- Adding or Updating a Single Alias
Recommended Maximum Number of Items/Security Identities per Hour
This does not imply that you should ever make one million Push API calls per hour.
Typically, you should:
- Start experimenting with the Push API by manually making a few “test” calls. At this point, you should only use the “single” push operations.
- Once you understand the basic concepts behind the Push API, you should manually make a few small “batch” push operations to get comfortable before automating the process.
- When you feel confident enough, you can start actually adding and/or updating the bulk of your Push source content by automating “batch” push operations (Add, update, and/or delete batch of items, Add, update, and/or delete batch of identities). Using these operations will allow you to push large number of items and/or security identities, while keeping your number of Push API calls per hour relatively low.