Night-shift schedule issue – Single Schedule ID generated instead of two entries -Urgent

[sathish]

Dear Team,
We are facing an issue with the recent behavior of the Schedule API for night-shift entries that cross midnight. Earlier, schedules were created day-wise, but now the system is merging both days into a single entry. Due to this change, we are unable to update or delete schedules correctly.

Issue Description
Night shift period:
Date: 25-11-2025 to 26-11-2025
Time: 18:00 PM to 02:30 AM

URL:
https://xxxxx.simprosuite.com/api/v1.0/ ... schedules/

We post schedules using two different API requests as shown below:
Day-1 POST request:

Code: Select all

{
    "Notes": "string",
    "IsLocked": false,
    "Staff": 1291,
    "Date": "2025-11-25",
    "Blocks": [
        {
            "StartTime": "18:00",
            "EndTime": "24:00",
            "ScheduleRate": 1
        }
    ]
}

Day-2 POST request

Code: Select all

{
    "Notes": "string",
    "IsLocked": false,
    "Staff": 1291,
    "Date": "2025-11-26",
    "Blocks": [
        {
            "StartTime": "00:00",
            "EndTime": "03:00",
            "ScheduleRate": 1
        }
    ]
}

Previous Behavior (Correct and expected)
Returned two separate schedule records:

Day 1 Response (Example):
Date: 25-11-2025 Time: 18:30 – 24:00
Schedule ID: 12568

Day 2 Response (Example):
Date: 26-11-2025 Time: 00:00 – 02:30
Schedule ID: 12569

This separation allowed us to:
1.Update individual days
2.Delete individual days
3.Maintain accurate day-wise reporting
4.Reflect proper hours per day

Current Behavior (Problem)
Instead of producing two separate schedules, the API returns:
Only ONE schedule entry
With Schedule ID: 25800

Combined duration:
25-11-2025 18:30 PM → 26-11-2025 02:30 AM
Additionally:
For 25-11-2025 we are getting complete response
No schedule entry returned for 26-11-2025
Response is completely empty for Day-2

Code: Select all

[
    {
        "ID": 25800,
        "Type": "job",
        "Reference": "1325-129",
        "TotalHours": 8.5,
        "Staff": {
            "ID": 156,
            "Name": "Sathish Kumar",
            "Type": "employee",
            "TypeId": 156
        },
        "Date": "2025-11-25",
        "Blocks": [
            {
                "Hrs": 2,
                "StartTime": "18:30",
                "ISO8601StartTime": "2025-11-25T18:30:00+11:00",
                "EndTime": "20:30",
                "ISO8601EndTime": "2025-11-25T20:30:00+11:00",
                "ScheduleRate": {
                    "ID": 2,
                    "Name": "Overtime 1.5x"
                }
            },
            {
                "Hrs": 6.5,
                "StartTime": "20:30",
                "ISO8601StartTime": "2025-11-25T20:30:00+11:00",
                "EndTime": "03:00",
                "ISO8601EndTime": "2025-11-26T03:00:00+11:00",
                "ScheduleRate": {
                    "ID": 3,
                    "Name": "Overtime 2.0x"
                }
            }
        ]
    }
]

Request
Can you guide to get the previous expected API behavior for night shift ?

[SimproAPITeam]

Hi there,

What you have provided is the expected behavior of our schedules feature, and this is how it works in the Simpro Suite UI as well. If you POST a schedule that is overnight, it should be one schedule. I would direct you to raise a ticket with support here:

https://helpdesk.simprogroup.com/#create-a-case to confirm your issue as well as provide more clarity if necessary.

Thanks,

[sathish]

Hi Team,
Could you please confirm if there is any updated API documentation available for handling night shifts ?

[SimproAPITeam]

Hi there,

You should be able to handle it on a block level and can update these blocks through the PATCH request which you can read more about here:
https://developer.simprogroup.com/apido ... d7e8a19e8c.

If you want to separate these to independently you can also use a GET request on the schedules endpoint which will independently list the schedules and you can read more about that here: https://developer.simprogroup.com/apido ... beac3576d6

Hope this helps,

Thanks,