Discussions

We are integrating our system with ServiceM8 using the API to reschedule existing jobs or job activities programmatically. We have reviewed the documentation but are facing issues with both n8n and Zapier approaches.

Specifically, we need your help to clarify:

1️⃣ What is the correct API endpoint to update the scheduled date and time of an existing job or job activity? Should we use /job, /jobactivity, or another endpoint?

2️⃣ What payload format is required to reschedule a job?
Examples we tried:

{ "job_is_scheduled_until_stamp": "YYYY-MM-DD HH:MM:SS" }
{ "start_date": "YYYY-MM-DDTHH:MM:SSZ", "end_date": "YYYY-MM-DDTHH:MM:SSZ" }
3️⃣ What authentication method is required for this API call? Is an X-API-Key sufficient or is OAuth mandatory (as seen in Zapier integrations)?

4️⃣ What identifier is needed: job_uuid or jobactivity_id? If only the job_uuid is available, can we reschedule it, or do we need to first retrieve the activity ID?

We have received repeated 401 Unauthorized and 404 Not Found errors, despite correct credentials and IDs.

Could you please provide:
✅ correct endpoint,
✅ required authentication method,
✅ a minimal working example (headers + payload) for rescheduling?

This would help us resolve the automation blockage.