Building on Informer

Informer is a platform as much as a product. Apps let you build whole applications inside it, for any business problem and not only reporting, with the platform's data, identity, AI, and security underneath. Everything Informer's own interface does runs through a public REST API, so your systems can drive it from outside. Those are the two big ways in. The rest are doors between your systems and Informer, and this page maps all of them.

Build inside InformerApps

Whole applications that live in Informer, for any business problem, with its data, identity, AI, and security underneath. Built with Claude Code, shipped in one command, carried to other instances by the Marketplace.

my-app/

informer.yamldata, roles, agents, widgets

server/its own API routes

migrations/its own database

webhooks/inbound events

tools/ · mcp/what AI may call

index.html · main.jsany Vite framework

Getting Started →TutorialsReference

Connect from outsideREST API

Everything Informer's own interface does, over HTTP, from any language: pull data out, push data in, automate the rest. A token scopes each integration to exactly the access it needs.

https://your-instance.entrinsik.com

POST/api/datasets/{id}/_search

POST/api/queries/{id}/_run

POST/api/assistants/{id}/_ask

POST/api/chats

GET/api/apps

GET/api/users

Getting started →All 39 areas

The whole map

Every door crosses the line between your systems and Informer in one direction or the other. Apps and Functions are the exception: that code runs on Informer's side of the line, which is why several doors are things an App gives you.

Your systemsInformer

Scripts, services, other products

REST API↓

Datasets, Reports, AI, Users: everything on screen

Claude Code, Claude Desktop, Cursor

MCP↓

Appan App's mcp/ tools

Slack, Stripe, GitHub, any service

webhooks↓

Appan App's webhooks/ handlers

Your own web app or CLI

OAuth 2.0↓

the API, as a signed-in user

People and pages without accounts

external links & tokens↓

an App, Report, or Dataset

MCP servers and APIs you host

Toolkits↓

Informer's AI

Third-party APIs, with OAuth

Integrations↓

Appan App's dependencies

Your code, on Informer's side of the line

Appswhole applications, with their own database, API routes, agents, and tools

FunctionsJavaScript in the data pipeline

Arrows point the way a connection is opened. Rows marked App are doors an App gives you.

Pick a door

I want to…	Use	Start here
Build an application that lives in Informer: a portal, a board, a workflow, a dashboard	An App	Getting Started
Pull Informer data into another system, or automate Informer from a script	The REST API	Getting started with the API
Let Slack, Stripe, GitHub, or any other service push events into Informer	An App's webhooks	Webhooks
Ask Claude Code, Claude Desktop, or Cursor questions answered from Informer data	An App's MCP tools	MCP
Let Informer's AI call tools you host	A Toolkit	Working with Toolkits
Sign users in to your own application or CLI with their Informer account	An OAuth 2.0 client	OAuth Client API
Show an App or Report to people without Informer accounts	External links and tokens	App external links, Report tokens
Pull a third-party API into an App with your users' OAuth credentials	An Integration dependency	Integration Dashboard
Reuse a calculation across queries, Datasets, and Reports	A Function (UDF)	Functions API
Build on an App someone else published to the Marketplace	A pack dependency	informer.yaml: pack
Install Apps others have published, or publish your own	The Marketplace	Marketplace
Move content between Informer instances	Bundles	Bundles API

Where things live

• Apps: getting started, tutorials by example, and reference for the Vite plugin, server routes, webhooks, deployment, and informer.yaml.
• API Reference: every endpoint, grouped by area, with request and response examples captured from a real server.
• Help Center: the product view of the same surfaces. Apps for developers is the big picture of the App codebase path, and Using the Informer API explains requests and tokens without assuming a developer is reading.