Services API Rate Limits
Learn the rate limits for the Services API.
This document lists the default rate limits that apply to the Services API.
Rate limits depend on multiple factors. An individual operation can have multiple rate limits. For example, a rate limit might depend on the selling partner account and also on the application that calls the Selling Partner API on behalf of the selling partner account. Requests are rate-limited by whichever threshold you reach first.
Note
The
x-amzn-RateLimit-Limitresponse header, if available, specifies the operation's rate limits per account-application pair. Thex-amzn-RateLimit-Limitdoesn't include other usage plan rate limits. For details, see How to find your usage plan.
For information about the rate-limiting algorithm, factors that determine rate limits, and how to find your rate limits, refer to Usage Plans and Rate Limits. For information about how to optimize your application for rate limits, refer to Optimize Rate Limits for Application Workloads.
In the following table, rates are in requests per second unless otherwise specified.
Services v1
| Operation | Rate limit per account-application pair | Burst (requests) |
|---|---|---|
getServiceJobByServiceJobId | 20 | 40 |
cancelServiceJobByServiceJobId | 5 | 20 |
completeServiceJobByServiceJobId | 5 | 20 |
getServiceJobs | 10 | 40 |
addAppointmentForServiceJobByServiceJobId | 5 | 20 |
rescheduleAppointmentForServiceJobByServiceJobId | 5 | 20 |
assignAppointmentResources | 5 | 20 |
setAppointmentFulfillmentData | 5 | 20 |
getRangeSlotCapacity | 5 | 20 |
getFixedSlotCapacity | 5 | 20 |
updateSchedule | 5 | 20 |
createReservation | 5 | 20 |
updateReservation | 5 | 20 |
cancelReservation | 5 | 20 |
getAppointmmentSlotsByJobId | 5 | 20 |
getAppointmentSlots | 5 | 20 |
createServiceDocumentUploadDestination | 5 | 20 |
Updated 29 days ago