When I’m trying to use a HTTP-Request to get some orders from Billbee, the json is not parsed correctly.
To explain that in more detail:
The CURL command is:
curl -L -o out.json -X Get -H “accept: application/json” -H “Authorization: Basic XXX” -H “X-Billbee-Api-Key: XXX” ‘https://app.billbee.io/api/v1/orders?minOrderDate=2024-07-04T00:00:00&maxOrderDate=2024-12-31T00:00:00&orderStateId=16’
When I test this, the output is a JSON. Here just the most important part of it:
{
"Paging": { ... },
...
"Data": [
{
...
"CreatedAt": "2024-08-22T00:00:00",
...
"BillBeeOrderId": 20000000079332415,
"BillBeeParentOrderId": null,
...
]
}
As you can see, the BillbeeOrderId ends with a 5
If I apply the same quest in n8n (could version 1.55.3): the result is different. In explicitly, the parameter BillBeeOrderId is different:
{
"Paging": { ... },
...
"Data": [
{
...
"BillBeeOrderId": 20000000079332416,
...
]
}
Of course, this leads to fatal errors in the whole workflow.
At first i tought, it is a problem of the API of BillBee, but then I tested it with curl and there, everything is correct.
BillBee’s support says, this could be a parsing error. The field id is returned as integer (long64). Since javascript has problems with long number chains.
But I don’t know how to correct that within n8n.
I also tried to change the response-format in the node (to text or file), but this won’t help. The most important parameter of the request always is returned incorrectly.
I would appreciate if someone could help.
Thanks in advance!
