We’re using the Add-on SDK diary endpoint to post attributed job-diary items from our add-on:
POST /api_1.0/diary.json
{
"job_uuid": "…",
"content": "PortalMEin: 3 materials staged. Open: https://app.example.com/job/…"
}
(scope publish_diary_items)
The docs note diary content is plaintext and “markup is displayed literally,” so we’re relying on the client auto-linking a bare URL.
What we see:
- ServiceM8 desktop web app: the URL in the diary item renders as a working, clickable link.

- ServiceM8 mobile app (iOS): the exact same diary item shows the URL as plain text — it’s not tappable and does nothing.

Expected: consistent link behaviour across desktop and mobile (or documented guidance on what’s supported).
Questions:
- Is URL auto-linking in add-on diary items intended to work on the mobile app, or is it desktop-only by design?
- Is there a supported way to include a tappable link in a diary item (a permitted markup form, or a structured field), or should we not rely on links in diary content at all?
- If links aren’t supported in diary items, is the recommended pattern to deliver the deep link via an add-on notification (
destination_url) instead, and keep the diary item as a plain audit record?
For context, external deep links we’ve since confirmed need com.servicem8://… (per the iOS Deep Links guide) rather than the internal servicem8:// — happy to share specifics if useful. Mainly trying to understand the intended behaviour for links inside diary items so we implement it the supported way.
Thanks!