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

**URL:** <https://community.servicem8.com/t/feature-request-read-only-phonecall-api-access-for-add-ons/1241>\
**Category:** API & SDK\
**Created:** [October 24, 2026, 4:53am UTC](https://community.servicem8.com/t/feature-request-read-only-phonecall-api-access-for-add-ons/1241 "2026-10-24T04:53:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![logan\_sole](https://avatars.discourse-cdn.com/v4/letter/l/97f17d/32.png) [@logan\_sole](https://community.servicem8.com/u/logan_sole)\
**Post date:** [October 24, 2026, 4:53am UTC](https://community.servicem8.com/t/feature-request-read-only-phonecall-api-access-for-add-ons/1241/1 "2026-10-24T04:53:21Z")

</div>

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:

- [https://developer.servicem8.com/discuss/63e59620209ed70025634e53](https://developer.servicem8.com/discuss/63e59620209ed70025634e53)
- [https://developer.servicem8.com/discuss/632fcca57abf3d0025398f79](https://developer.servicem8.com/discuss/632fcca57abf3d0025398f79)
- [https://developer.servicem8.com/discuss/661403c68474b1003b6025fb](https://developer.servicem8.com/discuss/661403c68474b1003b6025fb)

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

---

<div class="post-metadata">

**Author:** ![Cody](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/cody/32/52_2.png) [@Cody](https://community.servicem8.com/u/Cody)\
**Post date:** [October 27, 2026, 4:55am UTC](https://community.servicem8.com/t/feature-request-read-only-phonecall-api-access-for-add-ons/1241/2 "2026-10-27T04:55:02Z")

</div>

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](https://developer.servicem8.com/reference/listinboxmessages) 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](https://developer.servicem8.com/reference/post_event_webhook_subscription), 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
