Hi Jason,
Yes. We’ve added new read-only REST resources for job-related SMS and Email history, as announced in our May 2026 API update here: ServiceM8 API Updates - May 2026
The new endpoints are: GET /api_1.0/sms.json, GET /api_1.0/sms/{uuid}.json, GET /api_1.0/email.json, and GET /api_1.0/email/{uuid}.json.
Per the announcement, SMS requires the read_sms scope and Email requires the read_email scope, and both endpoints return merged inbound/outbound job history and support $filter including related_object_uuid (so you can filter to a specific Job UUID).
Example (from the announcement): /api_1.0/sms.json?$filter=direction eq inbound and related_object_uuid eq {job_uuid}.
If you’re seeing “sms is not an authorised object type”, that means the update hasn’t rolled out to your account yet. Logging a Support ticket via the Help menu in the Online Dashboard lets our team prioritise enabling it.
Thanks,
Cody