This worked yesterday, then it started returning 500 error codes. Now it returns success, but an empty list. Any ideas? Thank you!

@adamajet I'm sorry to hear that you're experiencing issues with your API calls. It sounds like there might have been a temporary server-side issue when you received the 500 error codes, which typically indicate a server error. Now that you're receiving a success response but with an empty list, it could be due to a few different reasons: 1. The data you're requesting might not be available or there might be a query parameter that is filtering out all the results. 2. There could have been a change in the API that affects how data is retrieved or formatted. 3. It's also possible that there's a bug or a temporary glitch in the system. To assist you further, I would need more specific information about the API call you're making, including the endpoint, the request payload (if applicable), and any query parameters you're using. With that information, I can help you troubleshoot the issue more effectively. Can you provide more details about the request you're making?

@Vapi Here is the request endpoint: https://api.vapi.ai/call/?assistantId=2258b9f9-a43c-48c2-a3bb-4d5e98d51478&createdAtGt=20240621&limit=100

@adamajet Thank you for providing the request endpoint. Based on the URL you've shared, it looks like you're trying to retrieve a list of calls associated with a specific assistant ID, filtering the results to only include calls created after a certain date, and limiting the results to 100 items. Here are a few steps you can take to troubleshoot the issue: 1. **Check the Parameters**: Ensure that the

assistantId

is correct and that the assistant has associated calls after the date specified by

createdAtGt

. 2. **Date Format**: Verify that the date format for the

createdAtGt

parameter is correct and accepted by the API. The format you've provided (

20240621

) might need to be in a different format, such as ISO 8601 (

YYYY-MM-DD

). 3. **API Documentation**: Review the API documentation to ensure that the endpoint and parameters are being used correctly. 4. **API Changes**: Check if there have been any recent changes to the API that might affect the response. 5. **Contact Support**: If the issue persists and you're unable to find a solution, it may be best to contact the API support team for further assistance. If you've already checked these and are still facing issues, please let me know if there's anything else I can do to assist you!

@Vapi I actually used the right date format 2024-06-20T13:40:23Z

@adamajet Great, using the correct ISO 8601 date format is important for the API to understand the request properly. Since you've confirmed that the date format is correct, let's consider a few other possibilities: 1. **Data Availability**: There might not be any calls that match the criteria specified in the query parameters. Double-check if there are calls created after

2024-06-20T13:40:23Z

for the given

assistantId

. 2. **API Status**: The API might be up and running (hence the 200 success status code), but there could be an internal issue affecting the data retrieval process. 3. **Caching Issues**: Sometimes APIs or the systems they interact with cache responses. If there was a temporary issue that has since been resolved, the cache might still be serving an outdated response. 4. **API Limits**: Ensure that you haven't hit any rate limits or data caps that might prevent the API from returning the expected data. 5. **Debugging**: If possible, use any debugging tools or logs provided by the API to gain more insight into what's happening with your requests. If you've checked all of these and the issue is still unresolved, it might be necessary to reach out to the API provider's support team for more detailed assistance. If you'd like, I can help you initiate a support ticket. Would you like me to do that for you?

Can you provide some more context?

@Sahil I get a list if I don't use any dates in the query string but the moment I add a date, nothing comes back even if the date was last year. https://cdn.discordapp.com/attachments/1254063766006399016/1254132363667963975/image.png?ex=66786148&is=66770fc8&hm=6fd7cbc9134d2f3730c406c605e10249b9ecf517eb8aab1ee749e9de5f5519f1&

Provide me the complete curl request in DM

@Sahil , I just tried it again and it works now. Thanks for looking into this.