mobieusCore API — mobieusHelp

The Help surface of the public REST API. Read + write tickets, queues, agents, canned responses, tags, help topics, notification preferences, audit log. Plus 8 AI hooks for reply suggestions, summary, sentiment, categorization, resolution prediction, knowledge-gap detection, audit Q&A, and canned-response generation.

The ticket + queue + agent + reply endpoints landed in API 1.2.0; canned responses, tags, help topics, notification prefs, audit, and AI hooks were added in 1.3.0 (2026-06-02).

Scopes

Quick start

# Create a tag
curl -X POST https://YOUR-TENANT.mobieus.io/api/v1/helpdesk/tags \
  -H 'Authorization: Bearer mc_live_...' -H 'Content-Type: application/json' \
  -d '{"slug":"refund","name":"Refund","color":"#dc2626"}'

# Have AI summarize an open ticket
curl -X POST https://YOUR-TENANT.mobieus.io/api/v1/helpdesk/ai/summary \
  -H 'Authorization: Bearer mc_live_...' -H 'Content-Type: application/json' \
  -d '{"ticket_id":1234}'

Tickets, queues, agents (1.2.0, unchanged)

See the existing ticket / queue / agent / reply endpoints in api-overview. Nothing about those endpoints changed in 1.3.0 — they're already comprehensive.

Canned responses (1.3.0)

Body for create:

{
  "slug": "refund-policy",
  "title": "Refund policy",
  "body_md": "Hi {{requester.first_name}},\n\nOur refund policy is 14 days. {{ticket.reference}} is within that window.\n\n— Support",
  "queue_id": null,
  "is_active": true,
  "sort_order": 100
}

Placeholders are Mustache-style; the agent reply composer substitutes at insert time.

Tags (1.3.0)

| GET | /api/v1/helpdesk/tags | helpdesk:read | List. | | GET | /api/v1/helpdesk/tags/{id} | helpdesk:read | Get. | | POST | /api/v1/helpdesk/tags | helpdesk:write | Create. | | POST | /api/v1/helpdesk/tags/{id} | helpdesk:write | Update. | | POST | /api/v1/helpdesk/tags/{id}/delete | helpdesk:write | Delete (also removes from every ticket). |

Help topics (read-only, 1.3.0)

| GET | /api/v1/helpdesk/help-topics | helpdesk:read | List active topics with name, slug, queue_id. |

CRUD for help topics lives in the admin UI — topics carry custom- field definitions that don't translate cleanly to a simple REST body.

Notification preferences (1.3.0)

| GET | /api/v1/helpdesk/notification-prefs?scope=tenant_default&scope_id=0 | helpdesk:read | | POST | /api/v1/helpdesk/notification-prefs | helpdesk:admin |

Scopes: tenant_default / agent / requester. Body for set:

{
  "scope": "tenant_default",
  "scope_id": 0,
  "event_key": "ticket.created",
  "channel": "email",
  "enabled": true
}

Audit log (1.3.0)

| GET | /api/v1/helpdesk/audit?event_key=&actor_kind=&cursor=&limit= | helpdesk:admin |

Returns up to 200 events per page (default 50). event_key filters by event type; actor_kind is agent / requester / system / api.

AI hooks (1.3.0, BYOK Anthropic)

All 8 hooks route through your tenant's mobieusAI configuration — the same Anthropic key your tenant already configured for Community Manager. If no key is set, every hook returns {"ok": false, "error": "gate_blocked"} (HTTP 200, JSON envelope, no 500).

Operator-facing hooks

All take {"ticket_id": ID} body except canned-generate which takes {"intent": "explain refund policy"}.

Admin-only hooks

| GET | /api/v1/helpdesk/ai/knowledge-gaps?days=30 | helpdesk:admin | ok + data.gaps[] — clusters of repeated unresolved questions across the last N days of tickets (mobieusKnow article candidates). | | POST | /api/v1/helpdesk/ai/audit-qa | helpdesk:admin | ok + text — answers a question about the last 200 audit events with event-id citations. Body: {"question": "..."}. |

Sentiment example

curl -X POST https://YOUR-TENANT.mobieus.io/api/v1/helpdesk/ai/sentiment \
  -H 'Authorization: Bearer mc_live_...' -H 'Content-Type: application/json' \
  -d '{"ticket_id":1234}'

{
  "ok": true,
  "data": {
    "overall": "frustrated",
    "confidence": 0.82,
    "signals": ["second follow-up", "wait time mentioned", "all-caps emphasis"]
  },
  "usage": { "prompt_tokens": 412, "completion_tokens": 87, "model": "claude-haiku-4-5-20251001" }
}

The usage block feeds your admin AI usage dashboard at Admin → AI.

Errors

The AI hooks never throw 500 on a failed AI call — they always return JSON with ok: false and an error code:

What's not in 1.3.0

• Rules engine CRUD via API (admin UI only for now).
• SLA-plan + business-hours calendar CRUD via API.
• Bulk ticket operations (close-all, reassign-all).
• Custom-field schema CRUD via API.

Related Pages