Skip to content
Median
Esc
↑↓navigate↵open⌘Jpreview
On this page

Management API

Everything the dashboard can do, over HTTP: the inbox, customers, the knowledge base, signals, the agent’s settings, and the numbers. Server to server only, and no CORS headers are sent.

Two credentials open it. MEDIAN_KEY acts as the organization and can do anything an admin can, except send invitations and change members. An MCP OAuth access token acts as the teammate who approved it, with that person’s role checked on every request.

Ids are strings. Pass them back exactly as you received them; an id that is not yours reads as not found.

Version 1.0.0
Base URLhttps://api.median.sh/v1

Account

Who a token is, and the setup acts: organizations and keys.

Conversations

The inbox: read threads, reply, and move conversations along.

Tool approvals

High risk tool calls waiting on a person, and tools run by hand.

Tool suggestions

Tools the agent went without, each written up as a brief.

Customers

Everyone who has written in, and what is known about each.

Knowledge

The agent’s library: documents, folders, the review queue, and crawls.

Signals

Bugs and suggestions customers reported, and their trackers.

Feedback

Raw notes from anywhere, read and placed on the signal lists.

Tasks

The board work is tracked on: its columns, the requests waiting on a decision, and how it is wired up.

Integrations

Email, Slack, Discord, GitHub, Notion, Linear: everything after the consent screen.

Site

How the public site looks.

Organization

The organization, its members, and invitations.

Agent

The AI agent’s name, personality, and autonomy switches.

Webhooks

Where the organization asked to be told what happened.

Analytics

The dashboard’s numbers and the analytics page’s charts.

Billing

API allowances, usage, invoices and the activity log.

Call

Any method of the MCP client, by name, over HTTP.

Docs

Median’s own documentation, searched and read.

Was this page helpful?