# How can be used send\_stream API?

**URL:** <https://community.sendbird.com/t/how-can-be-used-send-stream-api/11344>\
**Category:** API\
**Tags:** chatsdk\
**Created:** [July 20, 2026, 12:56pm UTC](https://community.sendbird.com/t/how-can-be-used-send-stream-api/11344 "2026-07-20T12:56:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Radka\_Dimitrova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/radka_dimitrova/32/6107_2.png) [@Radka\_Dimitrova](https://community.sendbird.com/u/Radka_Dimitrova)\
**Post date:** [July 20, 2026, 12:56pm UTC](https://community.sendbird.com/t/how-can-be-used-send-stream-api/11344/1 "2026-07-20T12:56:23Z")

</div>

We use a chatbot built on a different AI platform. We use Sendbird channels to store our conversations, and we would like to deliver the chatbot’s streamed responses into these channels.

When calling the following endpoint:

POST https://api-{application\_id}.sendbird.com/v3/bots/{bot\_userid}/send\_stream

we receive this error:  
“(Sendbird AI/Delight add-on) is not provisioned for this application; enable it in the Sendbird plan/billing or contact Sendbird.”

Could you please let us know:

1. Where in the dashboard (or through which process) can we enable/provision this for our application?
2. Is there an additional cost associated with enabling it, and if so, how is it structured?

Thank you for your help.

---

<div class="post-metadata">

**Author:** ![ChandramaniVyas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.sendbird.com/chandramanivyas/32/6111_2.png) [@ChandramaniVyas](https://community.sendbird.com/u/ChandramaniVyas)\
**Post date:** [August 14, 2026, 9:36am UTC](https://community.sendbird.com/t/how-can-be-used-send-stream-api/11344/2 "2026-08-14T09:36:02Z")

</div>

Hi Radka,

I was unable to reproduce the issue on my end. I also checked your account configuration, and everything appears to be set up correctly for you to use the send\_stream API.

Could you please give it another try and let us know if you are still experiencing the issue? If the issue persists, please share the latest error response along with the approximate timestamp, and we will investigate it further.