Hi,
It is possible to create a link without http(s) but its impossible to update it without http(s). That is confusing. Is http(s) mandatory? If so the documentation should say so and it shouldn’t allow a link creation without it.
Also is it possible to get something more explicit than a 500 error on that type of errors?
I lost like 2 hours on it 
Cheers
Would love to know more about this, so we can help. Where are you adding these links, and what do they refer to?
Hi @dipro,
I’m adding these links in a link type column.
I’m able to create a link using 127.0.0.1 but i can’t update a link using 127.0.0.1 I have to add http://127.0.0.1 to be able to update it.
IMO it should work the same on creation and update.
Hey Mathieu,
That’s interesting! In the UI, the link column will add the http:// prefix if your link doesn’t already contain it – I suspect this behaviour is causing the issue. I’ll pass this along to our developers as a bug. In the meantime, I’d suggest using http:// as a prefix to all links to ensure they go through 
Cheers,
Dipro
Hey @dipro,
Another weird behavior of the API. On an item I have a column amount which is a number column.
I create it with:
{ amount: 100 } // it works fine
I query it, I get:
{ amount: ‘100’ } // it gives me a string, fair enough I convert it to add my new amount to it
Then I update it:
{ amount: 200 } // it gives me an error (btw api errors are pretty helpless, always Internal Server Error)
I have to update it passing a string:
{ amount: ‘200’ } // it works
When I query it again I get:
{ amount: ‘“200”’ } // why??
Now I have to add a JSON.parse on it to manipulate the value inside.
Why different behaviors between creating and updating? Its very confusing.
Cheers,
Hey @Zalayeta – thanks for reporting this! I was able to reproduce this issue.
I’ll pass it along to our dev team to review – they will prioritize it alongside the other issues on our backlog. I appreciate you bringing this up.