Is there anyway to access the read only endpoint for sms / emails so that our ai. can handle the phone call and understand real time. Eg. it has access to booking times etc and notes at the moment but we had a client call asking where the tech is. the tech had already sms’d that they were late and then more recently that they were on the way. The client obviously hasn’t seen them and has called to ask where he is. If we had access to the read only endpoint our ai could have let them know rather than resulting in fallback for someone from the office to give them a call? Would be handy for the ai to have that history as well and jump into a call having all the info it needs?
Hi Jason,
For read-only access to message content via API, the REST API currently exposes the ServiceM8 Inbox via the Inbox Message endpoints (GET /inboxmessage.json to list, and GET /inboxmessage/{uuid}.json to fetch a specific message).
Those endpoints use the read_inbox permission and Inbox messages include a message_type of email or sms along with the message body (message_text / message_html).
If you also need to send updates from your integration, the Messaging API provides POST /platform_service_sms and POST /platform_service_email, and regardingJobUUID links the sent message to a job so it appears in that job’s Diary.
The Messaging API is only available to Public Applications and requires OAuth 2.0 (access token) to use.
On the customer-reply side, Two-Way SMS replies are added to the relevant job Diary (and replies for Completed + Paid jobs are also copied into your ServiceM8 Inbox), and Two-Way Email replies are also added to the job diary.
If the “tech is late / on the way” SMS you’re referring to are present as Inbox messages in your account, your AI can pull them via the /inboxmessage endpoints and use the timestamps/message text as call context.
Once you’ve confirmed whether those outgoing SMS are appearing in your ServiceM8 Inbox, reply here and we’ll point you to the best endpoint and scopes for your setup.
Thanks,
Cody