[Feature]: Request to Enable Nested Assistant API Endpoints

[Venukiran004]

The Feature

Description:
We are looking to utilize nested API endpoints for the assistant feature within our application. However, it seems that these endpoints are not currently enabled. Access to these endpoints is crucial for managing operations related to threads and runs effectively.

Required Endpoints:
POST /v1/threads/{thread_id}/messages/{message_id}
GET /v1/threads/{thread_id}/runs/{run_id}
GET /v1/threads/{thread_id}/runs/{run_id}/steps
POST /v1/threads/{thread_id}/runs/{run_id}/submit_tool_outputs
GET /v1/threads/{thread_id}/runs/{run_id}

Motivation, pitch

Our application relies on these nested API calls to manage essential assistant workflows. Enabling access to these endpoints is critical for ensuring smooth operation, allowing us to perform tasks such as posting messages, retrieving run details, and submitting tool outputs efficiently.

Twitter / LinkedIn details

https://www.linkedin.com/in/venukiran-sankar/

[krrishdholakia]

if this is for azure, you can just use the azure/ pass through route

[Venukiran004]

It's for OpenAI

[Venukiran004]

Hi @krrishdholakia,

I wanted to check if there’s an estimated timeline for when this might be addressed. Having an idea would help me plan accordingly on my end.

I appreciate any insights you could provide.