API-created Job Allocations Appear in Queue Instead of Staff Schedule

Originally posted by miko

I’m currently integrating with the ServiceM8 API and I’ve noticed that when I create a job allocation via the API, the job appears under the “Upcoming Bookings” queue instead of being placed directly in the Staff Schedule for the assigned staff member.

My goal is for the job to automatically appear in the staff’s daily schedule view (under Staff Schedules) at the specified date and time, rather than staying in the queue.

Could you please clarify:

Which API endpoint and parameters I should use to ensure the job allocation is placed directly in the staff schedule?

Whether there’s a specific field (e.g., start_time, end_time, or allocationwindow) that determines if a job appears on the schedule rather than the queue?

If any additional action is required after creating the job allocation (such as updating job status or setting a scheduling flag).

For context, I’m using the Create Job Allocations
endpoint, and my intention is to have the job displayed in the staff’s timeline (like the “Staff Schedules” tab in the dashboard) for a specific time slot.

Thank you for your help!

I am having the same issue. Were you able to fix this?

Hi,

For an exact time slot in the staff member’s schedule, use a scheduled Job Activity rather than a Job Allocation.

Job Allocations are for work assigned to a staff member within a booking window, not necessarily a fixed time slot.

If you do want to use Job Allocations, the relevant fields are staff_uuid, allocation_date, and allocation_window_uuid; allocation_date controls the future staff schedule date, and allocation_window_uuid defines the completion window.

So the usual fix is: create a Job Activity via POST /jobactivity.json with the job UUID, staff UUID, scheduled start/end dates, and the scheduled flag populated for fixed-time bookings; use Job Allocations only when you want a flexible booking window.

If the job is still sitting in a queue after creating a valid scheduled activity, email support@servicem8.com with the non-sensitive request/response details so we can check the account-specific behaviour privately.

Thanks,
Cody