# Route api creation of posts too many requests

**URL:** <https://meta.discourse.org/t/route-api-creation-of-posts-too-many-requests/304916>\
**Category:** Development\
**Tags:** rest-api\
**Created:** [April 22, 2024, 5:07pm UTC](https://meta.discourse.org/t/route-api-creation-of-posts-too-many-requests/304916 "2024-04-22T17:07:35Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![edu\_moura](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/edu_moura/32/379905_2.png) [@edu\_moura](https://meta.discourse.org/u/edu_moura)\
**Post date:** [April 22, 2024, 5:07pm UTC](https://meta.discourse.org/t/route-api-creation-of-posts-too-many-requests/304916/1 "2024-04-22T17:07:35Z")

</div>

We’re doing some testing with multiple users, doing topic queries, topic creations, and also adding replies to a topic. In the middle of the test, the post creation route started returning code 429, and it was no longer possible to respond to topics, but the other query routes, like, and the topic creation route, which are the same in this case, what changes is the attribute did not give 429.

Just to note, our personalized front calls our API, which in this API performs all the necessary actions in the discourse, we use it as an intermediary to process the information. Another point is that all tests are carried out with different users, using the functionality of adding the username to the route header. The only thing would be the IP itself because of the server that has the intermediate API

The question is, how can only the post creation part give the 429 problem, while all the others continued to work?

---

_[View the full topic](https://meta.discourse.org/t/route-api-creation-of-posts-too-many-requests/304916)._