Rate Limiting

The Publishers Management API enforces rate limiting per account. These limits help us provide the reliable and scalable API that our developer community relies on. These rate limits apply across all versions of the API.

Description Method Path Window Request Quota
All GET requests GET Any path starting with /{version} 60s 1080
All POST requests POST Any path starting with /{version} 60s 1080
All PUT requests PUT Any path starting with /{version} 60s 1080
All DELETE requests DELETE Any path starting /{version} 60s 1080
Line items bulk fetch per second GET /{version}/line-items 1s 5
Line items bulk update per minute PUT /{version}/line-items 60s 60
Creatives image upload per 5 seconds POST /{version}/creatives/image_upload 5s 5
Data GET requests GET Any path starting with /{version}/data 60s 10
Data POST requests POST Any path starting with /{version}/data 60s 5

Best Practices

  • Take advantage of the bulk update feature for the line item endpoints. This can reduce the overall number of calls you make and thus leverage rate limit more efficiently.

  • Request maximum “limit” in your requests: A limit on the number of objects to be returned, between 1 and 100 (default is 50).


Last updated July 21, 2021

TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.

© 2021 MoPub (a division of Twitter, Inc.)