# ServiceM8 API – Historical Job Data, Queue Events & Reporting Questions

**URL:** <https://community.servicem8.com/t/servicem8-api-historical-job-data-queue-events-reporting-questions/1228>\
**Category:** API & SDK\
**Created:** [October 7, 2026, 8:23pm UTC](https://community.servicem8.com/t/servicem8-api-historical-job-data-queue-events-reporting-questions/1228 "2026-10-07T20:23:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tom\_RESTATE](https://avatars.discourse-cdn.com/v4/letter/t/bb73d2/32.png) [@tom\_RESTATE](https://community.servicem8.com/u/tom_RESTATE)\
**Post date:** [October 7, 2026, 8:23pm UTC](https://community.servicem8.com/t/servicem8-api-historical-job-data-queue-events-reporting-questions/1228/1 "2026-10-07T20:23:43Z")

</div>

We’re developing a read-only management reporting add-on and I’m trying to establish which historical data can be obtained reliably through the supported API.

Has anyone implemented the following using the ServiceM8 API/Add-on Kit?

1. **Original job creation timestamp:** Is there a reliable immutable creation timestamp separate from Job `date`, which may represent created/scheduled date?

2. **Issued invoice/quote history:** Is there an endpoint/object that provides actual issued quote/invoice versions, issue timestamps, ex-tax/tax totals, credits and partial invoices, rather than relying on current Job totals?

3. **Queue history:** Can historical queue entry/exit transitions be retrieved, or does this need to be captured prospectively from `job.queued` / other events? If you’ve used `job.queued`, what payload does it provide?

4. **Native Xero tracking category:** Is there a supported way to retrieve the ServiceM8 Xero tracking-category selection other than observing `customfield_xero_tracking_cat_1` on the Job object?

5. **Incremental synchronisation:** Do changes to child records such as materials/invoices update the parent Job `edit_date`, or should each relevant object type be independently synchronised?

I’m looking specifically for supported API behaviour or practical experience rather than implementation advice. Example responses/endpoints would be appreciated.