# Calling API endpoints in multiple conversations

**URL:** <https://forum.rasa.com/t/calling-api-endpoints-in-multiple-conversations/64520>\
**Category:** Rasa Open Source\
**Created:** [November 17, 2024, 5:31pm UTC](https://forum.rasa.com/t/calling-api-endpoints-in-multiple-conversations/64520 "2024-11-17T17:31:23Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![thinkinnet](https://avatars.discourse-cdn.com/v4/letter/t/cc9497/32.png) [@thinkinnet](https://forum.rasa.com/u/thinkinnet)\
**Post date:** [November 17, 2024, 5:31pm UTC](https://forum.rasa.com/t/calling-api-endpoints-in-multiple-conversations/64520/1 "2024-11-17T17:31:23Z")

</div>

Hi all,

we have a general question calling API endpoints, especially if we cannot be sure if this endpoints have a reasonable respond time. What we see is that an API call is made by the action server itself so it is not independent for each conversation. This means that the complete action server waits for every API call that is made. So if there is an API call that takes a couple of seconds (for whatever reason), the action server is on hold and all other conversations are waiting as well.

Is there an in-build solution for this behavior or do we have to work with asyncio like solutions?

It would be sufficient to handle API calls conversation independent, so that other conversations don’t wait for API calls of other conversations.

We would appreciate your suggestions on this topic. Thanks in advance!

---

_[View the full topic](https://forum.rasa.com/t/calling-api-endpoints-in-multiple-conversations/64520)._
