Trying to make an API call to airtable to create a new table but make is unable to parse the JSON

[noor_dab]

I’m working on a scenario that watches records on an Airtable table, everytime a record is added the scenario lists bases, get the base with the name equal to the one from the record and then creates a new table in the base, now my problem is that i’m getting errors that don’t make sense on the last API call. I put my JSON string on the body of the API call and then i kept getting an error that says [422] Could not parse request body, i checked my JSON multiple times however i can’t find anything wrong with it, plus i followed the API documentation to the point but nothing!
Here’s some screenshots from my scenario :

[samliew]

Welcome to the Make community!

Can you please copy the JSON and paste it here in this forum?

I just want to help you double-check if it’s truly valid, using https://jsonformatter.org/

You’ll also need to format the JSON code properly otherwise it gets jumbled up and invalid:

• Either add three backticks ``` before and after the code, like this:

  ```
  <sup>JSON content goes here</sup>
  ```

• Or use the format code button in the editor:
  

[noor_dab]

{
    "name": "{{3.`ORDER #`}}",
    "fields": [
        {
            "type": "singleLineText",
            "name": "Order number"
        },
        {
            "type": "singleLineText",
            "name": "UPC/SKU"
        },
        {
            "type": "singleLineText",
            "name": "WU"
        },
        {
            "type": "singleLineText",
            "name": "Item description"
        },
        {
            "type": "singleLineText",
            "name": "Condition"
        },
        {
            "type": "number",
            "name": "Original QTY"
        },
        {
            "type": "currency",
            "options": {
                "symbol": "$"
            }
        },
        {
            "type": "singleLineText",
            "name": "Tracking"
        },
        {
            "type": "singleLineText",
            "name": "Shipment ID"
        },
        {
            "type": "currency",
            "options": {
                "symbol": "$"
            },
            "name": "Total Total original retail"
        },
        {
            "type": "number",
            "name": "of units"
        },
        {
            "type": "singleSelect",
            "options": {
                "choices": [
                    {
                        "name": "Shoes",
                        "color": "pinkBright"
                    },
                    {
                        "name": "Active Wear",
                        "color": "cyanBright"
                    },
                    {
                        "name": "General Merch",
                        "color": "purpleBright"
                    }
                ]
            },
            "name": "Type"
        },
        {
            "type": "number",
            "name": "Shoes QTY"
        },
        {
            "type": "currency",
            "options": {
                "symbol": "$"
            },
            "name": "Shoes Total"
        },
        {
            "type": "number",
            "name": "Active wear QTY"
        },
        {
            "type": "currency",
            "options": {
                "symbol": "$"
            },
            "name": "Active wear Total"
        },
        {
            "type": "currency",
            "options": {
                "symbol": "$"
            },
            "name": "General Merch Total"
        },
        {
            "type": "number",
            "name": "General Merch QTY"
        }
    ]
}

[samliew]

Everything checks out. There shouldn’t be any issue.

Make sure there are no trailing spaces before and after the first and last brackets.

For bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.

You can open a new ticket, or if you are unable to login for some reason, you also can reach support using the contact form on the website.

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

[noor_dab]

Hey, thank you for your response, i actually did all of the above, i even contacted airtable support, cause every other api call of their works just fine except for this one, despite the fact that everything i’ve done matches the documentation 100%. Anyway I will definitely keep you posted about it. Thank you again!