Discussions

Dear D-ID Support Team,

I am currently using your Stream Talk API for a school capstone project, and I’ve encountered a recurring issue regarding session expiration that has been quite frustrating and costly in terms of credits.

After about 2 minutes of inactivity, the session_id becomes invalid. When I attempt to send a new request using the same session (e.g., a talk-stream request), the API returns a 400 Bad Request. This has made it very difficult to maintain a smooth and stable conversation flow, especially since natural pauses longer than 2 minutes are common in our use case.

As this is a student project, I have limited credits available—and each time a session expires unexpectedly, it forces a new stream, leading to unnecessary credit consumption.

Could you please let me know:

Is there any way to extend the session duration, perhaps by sending periodic heartbeat requests or by calling an endpoint to keep the session alive?

If not, is there a recommended workaround to prevent sessions from expiring too quickly?

Would you consider adding a keep-alive or session refresh feature in the future?

I really appreciate the capabilities of your platform—it’s been essential for our project. But this particular limitation has been a serious blocker for our team, and any advice or support would mean a lot.

Thank you very much for your time and help.

Best regards,

Lisa