You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have started developing an API for a client's website who is switching their service from their current provider to BookingSync, and I have noticed that the documentation shows telephone numbers being sent as integers in the JSON, rather than strings.
Treating telephone numbers as numbers is not good practice, as telephone numbers are not 'numbers' they are strings of digits, and often begin with one or more leading zero which is then lost when stored as a number type in the JSON. They should be stored as a string and sent as a string to prevent data loss.
As I have not got to the testing phase, I have not been able to check whether JSON strings are accepted by the API - however if they are not I would strongly urge for this to be changed, and for the API Documentation to be updated accordingly.
The text was updated successfully, but these errors were encountered:
I have started developing an API for a client's website who is switching their service from their current provider to BookingSync, and I have noticed that the documentation shows telephone numbers being sent as integers in the JSON, rather than strings.
Treating telephone numbers as numbers is not good practice, as telephone numbers are not 'numbers' they are strings of digits, and often begin with one or more leading zero which is then lost when stored as a number type in the JSON. They should be stored as a string and sent as a string to prevent data loss.
As I have not got to the testing phase, I have not been able to check whether JSON strings are accepted by the API - however if they are not I would strongly urge for this to be changed, and for the API Documentation to be updated accordingly.
The text was updated successfully, but these errors were encountered: