Request limit

20 requests/minute
100 requests/day

Record limit

1,000 records/request.

If more than 1,000 records are to return, use follow on Pagination requests.


A pagination mechanism, always operational, is implemented.

Pagination principles:

Returns up to 1,000 records per request (page).

  • Response JSONs contain the following pagination related keys:
    • meta.total_items: The number of records to be returned by all pages combined. This represents the number of apps for which you have been granted the capabilities being queried.
      Pagination links (depicted in the JSON that follows) have the following keys:
      • links.prev: If there was a previous request: the request used to generate the previous page.
      • links.self: The current request: the request used to generate the current JSON (page)
      • links.next: The request required to get the next page. If there is no next key, this is the last page.

Use one of the following pagination control methods:

  • Best practice Use the links in the JSON: If the links.next key exists, use it to create a request to get the next page. Continue to do so until you receive a JSON without a links.next key.
  • Programmatically implement limit and offset parameters in conjunction with the total_items key.

Pagination links JSON example

  • The example that follows contains the result of the first request, consisting of the second request containing two records in the data section (not displayed).
  • The total number of records to return is 6.
  • The links.next key contains the request that returns the next page—records 5 and 6.
    "data": {[...]},   
    "meta": {
        "total_items": 6
    "links": {
        "prev": "https://hq1.appsflyer.com/api/mng/apps?capabilities=protect_360&offset=0&limit=2",
        "self": "https://hq1.appsflyer.com/api/mng/apps?capabilities=protect_360&offset=2&limit=2",
        "next": "https://hq1.appsflyer.com/api/mng/apps?capabilities=protect_360&offset=4&limit=2"