HTTP API Call gets back wrong data for just one field

[Chris-benchmarkets]

Bug Description

As you can see in the video, there is an API call we made for Bilbee API, and this API call gets back a wrong BilbeeOrderID (two numbers higher than it is in Bilbee itself). We double-check the call with Postman, and Postman returns the correct Bilbee Order ID, so there must be an issue in N8N.

https://www.loom.com/share/79370b6b2ff24336a80ec148101836cf?sid=e8149a61-0b3a-4006-a6f4-3ef315633ee3

To Reproduce

https://www.loom.com/share/79370b6b2ff24336a80ec148101836cf?sid=e8149a61-0b3a-4006-a6f4-3ef315633ee3

Expected behavior

https://www.loom.com/share/79370b6b2ff24336a80ec148101836cf?sid=e8149a61-0b3a-4006-a6f4-3ef315633ee3

Operating System

MACOS

n8n Version

1.65.2

Node.js Version

20.18.0

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @Chris-benchmarkets,

We have created an internal ticket to look into this which we will be tracking as "GHC-1723"

[Chris-benchmarkets]

@Joffcom I had to change the video link: https://www.loom.com/share/79370b6b2ff24336a80ec148101836cf?sid=e8149a61-0b3a-4006-a6f4-3ef315633ee3

[Joffcom]

Hey @Chris-benchmarkets,

The problem here is the ID 20000000061028236 is a bit bigger than the JavaScript max safe integer which is 9007199254740991 and that point numbers start to get a bit funky, Do you know if Billbee has a way to return a string instead of a number which would solve this problem for other systems that may run into it as well.

[Chris-benchmarkets]

Unfortunately, we are not able to influence how Billbee returns this data — we cannot get them to change this behavior. However, we have already implemented a workaround on our side to handle this limitation. Christian Sobek Von: Jon ***@***.***> Antworten an: n8n-io/n8n ***@***.***> Datum: Montag, 9. Juni 2025 um 16:25 An: n8n-io/n8n ***@***.***> Cc: benchmarkets GmbH ***@***.***>, Mention ***@***.***> Betreff: Re: [n8n-io/n8n] HTTP API Call gets back wrong data for just one field (Issue #14875) [https://avatars.githubusercontent.com/u/4688521?s=20&v=4]Joffcom left a comment (n8n-io/n8n#14875)<#14875 (comment)> Hey @Chris-benchmarkets<https://github.com/Chris-benchmarkets>, The problem here is the ID 20000000061028236 is a bit bigger than the JavaScript max safe integer which is 9007199254740991 and that point numbers start to get a bit funky, Do you know if Billbee has a way to return a string instead of a number which would solve this problem for other systems that may run into it as well. — Reply to this email directly, view it on GitHub<#14875 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BI34J6PKNEWYYGDYCPL526T3CWKM5AVCNFSM6AAAAAB3ZBER3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJVHE2TMOBUGY>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Joffcom]

Hey @Chris-benchmarkets,

That is perfect, I did look at the API docs for Billbee and it looks like they say they use a string so it could be that they are not following their API spec or I misread it 😓 either way I don't think this will be an easy fix for us due to how numbers work in javascript.

I will pass it back to the team for consideration anyway though.