Integrations
Fits the systems your business already runs
Kumiko is deliberately not a platform that wants to own your stack. It sends mail through your mail system, talks to whichever model endpoint you nominate, and exposes the same REST API its own clients are built on. Your existing departmental systems keep doing their jobs.
Integrations
A short, honest list
We would rather show you six things that genuinely work than a wall of logos where half are “coming soon”. Everything marked available is in the product today. If you need a direct connector into an existing system, talk to us about the API before you assume it exists.
Available
Microsoft 365 / Graph
Outbound mail goes through Microsoft Graph from a mailbox you nominate, so notifications and the daily brief arrive from a real address inside your tenant rather than a third-party relay that corporate IT will block.
Available
SMS notifications
Configure an SMS sender for the cases where email is not enough. An organization wide outage at two in the morning is not an inbox problem, and the person who needs to know is not at a desk.
Available
OpenAI-compatible model endpoints
Hosted providers or a local model server. Endpoint, model name, timeout and streaming are all set in the application. Swapping providers is a settings change, not a migration.
Available
REST API
The same JSON API the web and mobile clients use, token-authenticated, documented, and stable enough that we built a second client against it without changing the server. This is how problems get raised from a kiosk, a shared terminal or any internal tool that will never run the full interface.
Available
Real-time push (SignalR)
Live threads, participant updates and unread notifications over a persistent connection, so two people looking at the same problem see the same thing at the same time.
On request
Single sign-on
Directory-backed sign-in for self-hosted deployments. Talk to us about your identity provider before you plan a rollout. We would rather scope it honestly than list it as shipped.
Building against the API
Authenticate once, then every endpoint takes a bearer token. Raising a problem from another system is a single POST, which is how you capture problems from a kiosk, a shared terminal, an internal tool or anything else that will never run the full interface.
POST /ticket
Authorization: Bearer <token>
Content-Type: application/json
{
"collection": "3",
"description": "Expenses portal rejected a valid receipt again.",
"requesterEmail": "someone@example.com"
}The title, impact, priority and routing are all filled in server-side. See the documentation for the full endpoint reference. Read the docs
What is the problem you do not know about costing you?
Half an hour, your real problems, no slide deck. Bring one issue that keeps coming back and we will walk it through Kumiko end to end: capture, triage, fishbone, A3, countermeasure.