assistantId = c7cb70e9-cd98-40c3-af93-083fb9630bd6

> curl -G https://api.vapi.ai/call?assistantId=c7cb70e9-cd98-40c3-af93-083fb9630bd6&limit=5 \ > -H "Authorization: Bearer 579d6109-f6a9-43b5-9b1a-103186864e34" \ > -d assistantId=c7cb70e9-cd98-40c3-af93-083fb9630bd6 \ > -d limit=5 The /calls endpoint and Vapi Dashboard will not pull through the conversations for this assistant when querying directly by

assistantId

. This behavior started around 2 hours ago, the API was pulling through correctly previously. When querying for all assistants (removing that query param) the calls WILL pull through.

It looks like you're experiencing an issue with the

/calls

endpoint not retrieving conversations for the specified

assistantId

(

c7cb70e9-cd98-40c3-af93-083fb9630bd6

). This is a known issue where the endpoint does not differentiate results based on the

assistantId

, meaning it returns all results regardless of the filter applied. This bug has been reported, and it seems to have started recently, as you mentioned it was working correctly before. Unfortunately, until this issue is resolved, you may need to continue querying without the

assistantId

parameter to retrieve the calls. Here are a couple of suggestions: 1. **Check for Updates**: Keep an eye on any updates from Vapi regarding this issue, as they may provide a fix or workaround soon. 2. **Contact Support**: If this issue persists or if you need further assistance, consider reaching out to Vapi support for more specific guidance. Let me know if you have any other questions or need further help! 😊 Source: - [Detailed Report on Known Issues with the

/calls

Endpoint in Vapi API When Querying by

assistantId

](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331285157088333955)

this is now happening on a copy of this assistant (

a94f51e6-6cd1-49ed-8d9c-d8f64c2b16ba

), what is going on here? @Vapi Support Bot

It seems like you're still facing the same issue with the

/calls

endpoint not retrieving conversations for the

assistantId

(

c7cb70e9-cd98-40c3-af93-083fb9630bd6

), even on the copy of the assistant (

a94f51e6-6cd1-49ed-8d9c-d8f64c2b16ba

). This is indeed a known bug where the endpoint does not filter results based on the

assistantId

, returning all results instead. Since this issue has persisted, I recommend continuing to query without the

assistantId

parameter for now. Here are a couple of steps you can take: 1. **Monitor for Updates**: Keep an eye on any announcements from Vapi regarding a fix for this issue. 2. **Reach Out for Support**: If the problem continues or if you need more specific assistance, consider contacting Vapi support for further guidance. If you have any other questions or need more help, feel free to ask! 😊 Source: - [Detailed Report on Known Issues with the

/calls

Endpoint in Vapi API When Querying by

assistantId

](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331285157088333955)

> This is indeed a known bug where the endpoint does not filter results based on the assistantId, returning all results instead. This is not the behavior I am experiencing, the /calls endpoint isn't returning ANY results when filtering by

assistantId

Could you please provide more details about the specific request you're making, such as any error messages or status codes you're receiving? Additionally, have there been any recent changes to your API configuration or environment that might have affected the behavior? Source: - [Detailed Report on Known Issues with the

/calls

Endpoint in Vapi API When Querying by

assistantId

](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331285157088333955)

@LBThree please remove your API Key.