Menu

Mattering API reference

Every endpoint of every Mattering app: the route, what it accepts, what it returns, and how to authenticate. Generated from the code that serves the requests, so what you read here is what the API does today.

464

documented endpoints across 14 apps

163

MCP tools on the one Mattering gateway, plus 7 identity tools

2

tiers per app: the User API for your keys and agents, and a service tier for Mattering's own apps

Start here

Three steps get you from nothing to your first response.

  1. 1

    Create an organization API key

    An organization admin creates a mat_ key on the Platform API keys page. The key acts as its creator, inside one organization. See Authentication.

  2. 2

    Find your space

    Most endpoints take a space_id. Every app has a spaces endpoint that lists the ones your key can see.

    curl "https://sales.mattering.io/api/user/v1/spaces/" \
      -H "Authorization: Bearer $MATTERING_API_KEY"
  3. 3

    Read the app's reference

    Each app page lists its resources. Each resource page shows every endpoint with its parameters, body keys, response shape, error codes and a curl sample.

Apps

One page per app. The shape score counts how many of six Base API Template rules the app meets today (versioned prefixes, one route list on both tiers, the data and meta envelope, paginated lists, stable error codes). A lower score means the app's responses still follow its own older conventions, which the app page describes.

Mattering Productivity

Spaces, projects, tabs, widgets, tasks, batches, custom fields, presets, knowledge bases and query endpoints for the Productivity app.

62 endpoints in 26 resources, 53 MCP tools

Mattering Sales

Businesses, contacts, deals, pipelines, notes, tasks, meetings, files, activities, personas, custom fields, custom objects and campaigns for the Sales CRM.

56 endpoints in 22 resources, 35 MCP tools

Mattering Automations

Workspaces, Data Studio datatables, read-only node execution and agent invocation on the user tier; automations, secrets, connectors, telephony and the canvas builder on the service tier.

81 endpoints in 15 resources, 22 MCP tools

Mattering Agents

Agents, grants, knowledge sources, schedules, triggers, runs and the voice and browser runtime surface. Service tier only until the user tier is mounted.

36 endpoints in 13 resources, 5 MCP tools, service tier only

Mattering Comms

Channels, messages and search for Mattering Comms, plus the service-only call control surface agents use.

22 endpoints in 9 resources, 6 MCP tools

Mattering Forms

Forms, fields, submissions and cross-app mappings for Mattering Forms.

14 endpoints in 11 resources, 9 MCP tools

Mattering QR

QR codes and short links, their aliases and routing rules.

13 endpoints in 9 resources, 11 MCP tools

Mattering Calendar

Event types, live slot feeds and bookings for Mattering Calendar.

15 endpoints in 9 resources

Mattering Contracts

Envelopes, recipients, events and sending for Mattering Contracts e-signature.

13 endpoints in 8 resources

Mattering Analytics

Datasets, dashboards and tile data for Mattering Analytics.

14 endpoints in 9 resources

Mattering Networking

Settings, prep sheets, rules, stories, topics, prompts, debriefs and drills for Mattering Networking.

18 endpoints in 12 resources

Mattering Mastery

Scaffold surface: a ping and a placeholder curricula listing.

6 endpoints in 6 resources

Mattering Platform

The file service (every upload in every app is a managed file) and the organization custom field registry.

53 endpoints in 4 resources, 22 MCP tools

Mattering Auth

Login, tokens, JWKS, organizations, teams, workspaces, apps, entitlements, plans and organization API keys. Django REST Framework class-based views.

61 endpoints in 8 resources

Concepts

The rules that apply to every app, written by hand and kept beside the generated reference.

How this reference is built

A generator in the Mattering repository reads each app's URL tables and the view functions behind them, records the HTTP methods, query parameters, body keys, response shapes, error codes and pagination it finds, and writes the result as data the website renders. A continuous integration check fails any change that leaves this reference out of date with the code.

Because the reference is read from code rather than written about it, a missing description is shown as missing rather than filled in. Where a view has no docstring yet, the summary is a plain statement of its methods and resource, marked as generated. Response shapes are skeletons: field names come from the serializer, example values are placeholders.

The service tier page shows the same data from the operator's side: which endpoints are service-only, and what each app still has to change to match the shared API standard.

Operator-only surfaces: Mattering Website.

Start Free Explore our Products