Skip to main content

API Date Format Changes When Using Service User Authentication and humanReadable

  • March 9, 2026
  • 0 replies
  • 22 views

If your API response is returning dates in dd/MM/yyyy instead of the standard yyyy-mm-dd, this is expected behavior when using a service user with the humanReadable parameter.

By default, Bob’s API returns date fields in the standard machine format: yyyy-mm-dd

However, in your request, you’re using: humanReadable: "replace", the system formats date values as human-readable strings instead of the standard API format.

The service user authentication is not tied to a real user profile. Because a service user doesn’t have a site, locale or have personal display settings Bob applies a consistent default format for human-readable payloads.

The defined default human-readable date format is: dd/MM/yyyy.

 

This format is the initial base format defined in Bob’s underlying database configuration for most tenants.

* Is not configurable

* Cannot be changed to mm/dd/yyyy

* Does not follow employee site settings

* Does not follow UI display preferences

 

If you need the standard API format (yyyy-mm-dd), remove the humanReadable parameter from your request.