# App Search Document Indexing API rate limit

**URL:** <https://community.swiftype.com/t/app-search-document-indexing-api-rate-limit/723>\
**Category:** API\
**Created:** [June 5, 2018, 5:47pm UTC](https://community.swiftype.com/t/app-search-document-indexing-api-rate-limit/723 "2018-06-05T17:47:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![apps](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@apps](https://community.swiftype.com/u/apps)\
**Post date:** [June 5, 2018, 5:47pm UTC](https://community.swiftype.com/t/app-search-document-indexing-api-rate-limit/723/1 "2018-06-05T17:47:38Z")

</div>

I was not able to find any rate limit documentation for document indexing.

Can I be provided the rate limit for document indexing api calls? I am assuming that there is one.

Thanks,  
Andrew

---

<div class="post-metadata">

**Author:** ![joshuabalentine](https://avatars.discourse-cdn.com/v4/letter/j/74df32/32.png) [@joshuabalentine](https://community.swiftype.com/u/joshuabalentine)\
**Post date:** [June 7, 2018, 1:12pm UTC](https://community.swiftype.com/t/app-search-document-indexing-api-rate-limit/723/2 "2018-06-07T13:12:49Z")

</div>

Did you see [this page](https://swiftype.com/documentation/site-search/rate_limiting)? It does not provide the actual limit, but it does mention that it should be high enough not to bother most people.

If you meant a crawler-based engine, the crawler supports the `Crawl-delay` directive in the [robots.txt file](https://swiftype.com/documentation/site-search/robots).

---

<div class="post-metadata">

**Author:** ![apps](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@apps](https://community.swiftype.com/u/apps)\
**Post date:** [June 7, 2018, 5:29pm UTC](https://community.swiftype.com/t/app-search-document-indexing-api-rate-limit/723/3 "2018-06-07T17:29:40Z")

</div>

Hi Joshua,

I was looking for something like requests per second for the documents post API.

I did a stress test yesterday with 10 document post requests per second. The API held up. I’s unlikely we will go higher that.

Thanks,  
Andrew
