simPRO API Forum

Description:
One of our Simpro clients is experiencing an issue when creating a new Job Cost Center Schedule. The error occurs specifically when the shift component starts at midnight ("StartTime": "00:00") and getting response as null.
API Detail:
POST request:https://xxxxxxxx.simprosuite.com/api/v1 ... schedules/
Request Body:
{
"Notes": " ",
"IsLocked": false,
"Staff": xx,
"Date": "2025-08-25",
"Blocks": [
{
"StartTime": "00:00",
"EndTime": "06:30",
"ScheduleRate": xx
}
]
}

Response:
{
"errors": [
{
"path": null,
"message": "",
"value": null
}
]
}

Additional Notes:
If "StartTime": "00:00" does not work but "StartTime": "00:15" works fine, then the issue seems to be specifically with scheduling at exactly midnight
Tested with other jobs and overnight shifts, which passed correctly.

Hi Sathish,

That's a fantastic bug report, very clear and well-detailed. We've encountered similar edge-case issues with time and date values in the Simpro API before.

The fact that "StartTime": "00:15" works while "StartTime": "00:00" fails with a null error response strongly suggests a bug in the API's backend validation or processing logic specifically for the midnight value.

Sometimes, systems can be finicky with 00:00 as it can be an ambiguous value (the very end of one day or the very start of another), and it looks like it's failing a validation check that any other time would pass. The empty error message is also something we've seen. It makes debugging these issues much harder than it needs to be.

Immediate Workaround for Your Client

While waiting for an official fix from the Simpro team, your client can implement a very simple workaround that should unblock them immediately:

Instead of using 00:00, have them use 00:01.

This one-minute difference is usually negligible for scheduling purposes but is almost certain to bypass the specific validation bug affecting the midnight timestamp.

Example Workaround Request:
Hopefully, the Simpro developers can log this and get a fix in place. A more descriptive error message in the response would be a huge help for everyone in the future, too.

Hope this helps you and your client!

Best regards,

Gary

Hi Team,

As per the suggested workaround, we tried replacing 00:00 with 00:01.
However, this did not resolve the issue. We still received the following error:
Message "StartTime minute must be one of '00', '15', '30', '45'"
Request Reposnse:

Hi sathish,

Im able to post schedule block starting from "00:00" just fine,

Are you able to share your build info with the exact endpoint and response body so we can do further investigation ?

Just send it to us privately.

Thank you!

Hi Team,

I’ve shared the exact endpoint and response body privately.
Kindly get back to us as soon as possible.

Thank you