Skip to content

Build your own app

Build on Infinized.

Your own app on the API, with sign-in through Infinized. It receives what your flows deliver and can give Pal tools of its own.

Book a demoFor developers
A delivery, as your endpoint sees it
POST https://your-app.example.com/hooks/infinized
X-Infinized-Event: component.delivered
X-Infinized-Delivery: 6f1c1e6e-...
X-Infinized-Signature: sha256=<hex digest of the raw body>
Content-Type: application/json

{
  "event_id": "6f1c1e6e-...",
  "event": "component.delivered",
  "organization_id": 4,
  "data": { },
  "sent_at": "2026-10-09T06:12:03+00:00"
}

What an app gets.

Three things, the same for our apps as for yours.

Sign in with Infinized
People sign in with their own Infinized account. Your app keeps no password and sees their name, e-mail address and the workspaces it is connected to. We set your app up as a sign-in client together with you.
Deliveries over signed webhooks
An owner or admin connects a workspace, and its flows deliver to your app. Every delivery is signed with the connection’s secret, and connecting again issues a new one. Deliveries can be read back for 30 days.
Tools for Pal
Your app can offer Pal tools of its own, the way Insights lets Pal build dashboards. Each call reaches your app signed and names the person, so your app decides what they may do.

API

Or start from the API.

A smaller app needs no sign-in of its own. A key, the channel API and signed events take you a long way.

Your own front end
Your own app starts a flow through the channel API. A customer conversation is a trigger like any other, and the customer sees an AI notice.
Keys with scopes
A key gets named abilities, is tied to a real person and stops working when that person leaves the organisation.
Signed events out
Subscribe an endpoint to the events you care about. Each delivery carries the event name, a delivery id and a signature over the body.
How to check a signature
Webhook events · 13

The events an endpoint can subscribe to.

  • task.completed
  • task.failed
  • approval.pending
  • conversation.reply.completed
  • flow.notification
  • run.completed
  • run.failed
  • flow.run.completed
  • flow.run.failed
  • approval.resolved
  • conversation.closed
  • alert.raised
  • component.delivered

From outside, the same rules

Control stays with you.

Approvals, budgets and the audit trail apply to everything your app starts, exactly as they do inside.

Budgets
A run your app starts counts against the workspace, like any other.
Approvals
An action that waits for a person still waits for a person.
Audit trail
What happened, which model did the work and who decided, in one record.

Tell us what you want to build.

We start by listening to your question. Then we show you a demo that fits your organisation.

Book a demoFor developers