Hi @jacobmolby, welcome to the community!

For what it’s worth, and with a bit of selection bias here, I’ve only seen it represented as a decimal (e.g. 11.95).  If you look at the examples in the API, all the numeric and float values are represented this way - so I’m at least confident that would work. If it is indifferent to your code, I’d just use decimals instead of commas unless there are some regionalization/localization requirements. 

Interested to hear an official answer here!

@retention Thanks that’s also what we do now (since it’s an american platform), I just wanted to be sure since most of our customers are from the european mainland where 11,95 is the most common format.

But an official answer would be nice (and it should probably be added to the spec.)

Hi @jacobmolby!

@retention’s intuition was spot on, per usual. Right now, we only accept number values (like prices) in decimal format. Good call on the specs - I will make a request to the team that handles our documentation to have that included .

Thanks for using the Community!

- Brian