Jobactivity start_date is too old and not valid error

API & SDK
1

We are trying to migrate jobactivity data from an old legacy system to servicem8. This includes past client job history going back 10 years. We are getting the following error when posting to the jobactivity api end point a job with a start_date older than 2 years

{

"errorCode": 400,

“message”: “start_date is too old and not valid”,

“documentation”: “Please refer to https://developer.servicem8.com/llms.txt for developer documentation.”

}

Does anyone know what the un-documented restrictions are on start_date and have a recommendation on how to load legacy job data

I’m asking as it’s a legal requirement in the UK to maintain these records for up to 7 years.

2

Hi Aaron,

In ServiceM8 terms, JobActivity is the API entity behind both Scheduled Bookings and Recorded Time (check-in), so it’s fundamentally schedule/time-tracking data rather than a general-purpose historical event log.

For importing 7 to 10 years of legacy history into ServiceM8, we’d avoid trying to recreate that history as JobActivity rows - it’s against best practice and should be used for current and future schedules, and instead attach it to Jobs as job notes (and attachments where needed).

Thanks,
Cody

3

Thanks for the reply

Couple of questions from your reply:

→ where would you suggest putting the date / time the job took place? There doesn’t appear to be a field to a natural field for this in the job endpoint

→ if I create a job for today, with a jobactivity, what happens to the jobactivity in the future? If you’re blocking creation of past jobactivities where the start_date is greater than the cut off period does a future jobactivity have an expiration date where it’s deleted or no longer visible?

Thanks