@Matilda Hello! It's great to hear that you're working on automating a dynamic squad. The 400 status error typically indicates that there's something wrong with the request you're sending, such as a bad syntax or missing parameters. To assist you better, I'll need to see the JSON payload you're working with. Could you please provide the JSON payload you're using for the dynamic squad creation? Once I have that, I'll be able to help you troubleshoot the issue more effectively.

@Matilda It seems like there might have been a misunderstanding. If you're ready to provide the JSON payload or if you have any other questions regarding the Voice API or any other support you need, feel free to share the details, and I'll do my best to assist you!

I've shared the JSON Payload twice

@Matilda I apologize for the confusion, but it seems there might be a technical issue as I'm unable to see the JSON payload you've mentioned. Could you please try sharing it one more time? Make sure to include the JSON structure so I can review it and help you resolve the 400 status error you're encountering with your dynamic squad automation.

@Matilda It appears there might be a technical glitch preventing the JSON payload from coming through. If you're still facing issues with sharing the payload here, you might want to check the formatting or try to describe the structure and the specific part of the payload where you think the issue might be occurring. Alternatively, if you're unsure about the structure or the parameters required for your dynamic squad automation, I can provide general advice: 1. Ensure that all required fields in your JSON payload are present and correctly named. 2. Check that all values are of the correct type (e.g., strings, numbers, booleans) as expected by the API. 3. Validate that nested objects and arrays are properly formatted. 4. If you're using member overrides, make sure that the syntax matches the API documentation and that you're using the correct property names. If you're able to share more details or the error message that comes with the 400 status, I can offer more targeted assistance. Please let me know how you'd like to proceed!

i pasted the JSON severally (as a message.txt) but you cant seem to view it how else can i share it?

@Matilda I'm sorry for the inconvenience. If pasting the JSON directly into the chat isn't working, you could try describing the structure of your JSON payload instead. For example, you could outline the keys and the type of values you're including, and where you're using the assistant or member overrides. Alternatively, you could provide a high-level description of the steps you're taking to create the dynamic squad and where in the process you're encountering the 400 error. This might give me enough context to help you troubleshoot the issue. If these options are not suitable and you require a direct way to share files, you might need to reach out to the support team through the official channels provided by the platform you're using. They may have a file-sharing option or a secure method for you to submit your JSON payload for review.

Ive uploaded a txt with the JSON payload https://cdn.discordapp.com/attachments/1330961439267229696/1330965977080401970/Dynamic_Squad_outbound_call_JSON_Payload_-_discord.txt?ex=678fe629&is=678e94a9&hm=dc0a95677b7a9f652c806b3f34e36e0b02ad75a8effc479508fd376e559d11c1&

@Matilda I'm sorry for the confusion, but it seems I'm still unable to view the uploaded txt file with your JSON payload. To ensure we can proceed and address your issue, could you please try describing the structure of your JSON payload in text form here? You can list the keys and types of values you're using, and any specific areas where you've implemented overrides. For example, you might describe it like this:

json
{
  "teamName": "string",
  "members": [
    {
      "id": "number",
      "name": "string",
      "role": "string",
      // ... other member properties
    }
    // ... other members
  ],
  "settings": {
    // ... settings properties
  },
  // ... other properties
}

This way, I can get an idea of what your payload looks like and help you identify where the issue might be. If you're getting a 400 error, it's often related to missing required fields, incorrect data types, or syntax errors in the JSON structure.

@Shubham Bajaj kindly assist when you can

@Matilda Hey! Could you please provide a description of the issue along with the following information: - The curl request - What response you expected to get - What error response you actually got instead This information would help me track down and resolve the issue. Thanks!