I am trying to connect some products of our Shopify e-commerce to another e-commerce using Parabola API Export. This is the simplest configuration:
However, when I run the process, it shows this error:
I am new using this tool and my knowledge about JSON and API is limited. Any idea about where is the fault? I was testing the system against a MOck server and it was working with no errors.
Hi @Manuel! I see youâre getting a 422 - Unprocessable Entitle Error. This means that the request was correct, but there was a problem with what you asked the API to do.
From your screenshot, Iâm seeing the APIâs error message says, "The 0.currency field is required" and so on. From what I can tell in your screenshot, it looks like youâre mapping all the required fields.
Is it possible that the field names for your API is actually something like, 0.currency, 0.manufacturer, 0.manufacturer_sku, 0.price, 0.sku, 0.title?
If youâre able to link us to the API docs youâre referencing, we can take a closer look!
Hi @sachi, I have changed the destination fields, but it was not successful.
You can find the information about APi in this link:
Hi @Manuel - Thanks for giving that a try and sending the documentation over.
I learned that the 0. means that its parsing our request as an element of an array and itâs indicating that it failed in the 0th position, when trying to export the first row of data. Sorry for misdirecting you!
Took a look at the docs and your Body section looks mostly correct. Can you try wrapping your entire Body section with square brackets [ ]?
Let me know how that goes!
Hi @sachi,
Thanks for your support, now it works! Sincerely, I wrapped it initially but I should make another mistake and though it was due to the square brackets.
Regards.
Hi @sachi,
It looks the file arrives, however the endpoint reports there is only on row of data in the file and that is the last one. Any suggestion?
only one row of dataâŚ
Hey @Manuel - Interesting, it seems like the API isnât allowing us to export row-by-row and instead needs all the data in a single request.
To workaround this problem, please add an Insert Column step and a Merge Values step right before your Send to API step.
In the Insert Column step, weâre going to create a new column that replicates the body youâre sending in your API step minus the square brackets [ ], like so:
In the Merge Values step, weâre going to create a comma-separated blob of the new API Body column you created with the Insert Column step.
, (with no space).Once you do have a single cell that contains all the data youâre trying to export, update the body of your API Export step to just be:
[{new_merge_value_column}]
That should do the trick, and export all the data to the API in a single request. Let me know how that goes!
Awesome! Glad to hear it 
Hey, has the Merge Values step been renamed or removed? I cannot find a way to combine the newly created API Body column into a single cell as described. Thank you.
Hi @Gregory_Parsons 
yes, it has been renamed to Merge duplicate rows.
(The Insert column step was also renamed to Insert text column.)
Thanks, can you assist in configuring the Merge Duplicate Rows Step to achieve the result claimed in the discussion - i.e. achieving all data in one âcellâ resulting in a âSend to APIâ Step with a single API Request output?
I have only been able to achieve all rows being sent separately.
Thank you
@Gregory_Parsons sure thing! Hereâs how to configure this:
2 Steps: Insert text column - > Merge duplicate rows
(Double-click on screenshot to enlarge/zoom in. Note: in Insert Text Column Common value section, the underlined red {" } is auto-formatting that will be skipped during the stepâs function.)
The Insert text column step adds two columns: (1) an API Body column that replicates the Body Request youâd send in a Send to an API step and (2) a Merge column with the value of 1 (to help the following step merge values). Then in the connected Merge duplicate rows step, merge API body per unique value in Merge column by the dimeter of , comma.
