Feature request: read-only PhoneCall API access for add-ons

Hi ServiceM8 team,

We build a reporting add-on for ServiceM8 businesses. When an OAuth add-on requests phonecall.json, the API returns “PhoneCall is not a publicly documented object type”, so add-ons can’t report on ServiceM8 Phone at all.

We’re requesting that PhoneCall be added to the public API with a read-only OAuth scope (for example read_phone_calls).

Why it matters
For trade businesses, a missed call is often a lost job. Customers want to see:

  • Inbound, outbound and missed calls by day, hour and staff member
  • Which missed calls were returned, by whom, and how quickly
  • After-hours call volume
  • How many calls became jobs

Fields needed (read-only)

  • Call type and call status
  • Timestamp and duration
  • From and to (number or display name, and whether it’s a client or staff member)
  • Call group and after-hours flag
  • Call returned: by which staff member, and when
  • Related job or client
  • AI call summary

Optional, as a separate scope: voicemail transcripts and recording attachments.

Read access only. No create, update or delete. A webhook for new calls would be a bonus, but polling with an edit_date filter would work fine.

This has come up several times on the forum without an answer:

Could the team let us know whether this is on the roadmap? If you need this too, please add a reply so the demand is visible.

Thanks,
Logan

1 Like

Hi Logan,
The public API doesn’t currently expose PhoneCall records, a read_phone_calls OAuth scope, or a dedicated new-call webhook. The read-only call-log access you’re requesting, including structured call metadata, AI summaries, transcripts and recordings, isn’t currently available through a PhoneCall API.
There is a narrower option for Inbox-based workflows: the Inbox API supports messages with message_type: "phone_call". You can list messages with GET /api_1.0/inboxmessage.json and retrieve an individual message with GET /api_1.0/inboxmessage/{uuid}.json, using the read_inbox OAuth scope. These responses include fields such as timestamp, message_text, regarding_company_uuid and converted_to_job_uuid. This is access to Inbox messages, not a complete call-history reporting API.
For notifications about new Inbox messages, there’s also the inbox.message_received event, but it isn’t a dedicated event for every Phone call.
Your request clearly sets out the reporting workflow and the separation between basic read-only access and more sensitive recording/transcript access.
We’ll confirm the roadmap position for this request with the team.
Thanks,
Cody