Developer portal

The contract behind the silence

This describes how you integrate with MarketMute: the identity vault, suppression lookups before sending, signed webhooks, and the security model. The contract file is the source — these pages explain it.

Go to the API reference Suppression for B2B

Contractv1

Specification: OpenAPI 3.0.3
API version: 1.0.0
Production: api.marketmute.com/v1
Staging: staging.marketmute.com/v1
Auth: Bearer (OIDC)
Source file: marketmute.openapi.yaml

Register

Five departments. Each one covers a part of the contract.

Getting started

The first call

Everything goes through a Bearer token from Zitadel. The public app uses PKCE; a B2B integration uses a service account with scopes.

Start sequenceA-01

From token to response

Get a token
OIDC against Zitadel. Service accounts get exactly the scopes the integration actually needs — nothing more.
Call v1
The base URL carries the version. Staging runs the same contract as production.
Generate the client
Don't write the types by hand. The contract file lives in packages/contracts/openapi/marketmute.openapi.yaml and the clients are generated with scripts/generate-contracts.sh.

Verify accessbash

# Bearer token from Zitadel (OIDC)
curl -sS https://api.marketmute.com/v1/me/identity \
  -H "Authorization: Bearer $MARKETMUTE_TOKEN" \
  -H "Accept: application/json"

Scope of the contract

Scope

Counted straight from the contract file.

6Operations

5Resources

2Environments

0Raw PII in responses

Reading the register…

The contract behind the silence

Register

API reference

Suppression

Webhooks

Security

Changelog

The first call

From token to response

Get a token

Call v1

Generate the client

Scope

The contract behind the silence

Register

API reference

Suppression

Webhooks

Security

Changelog

The first call

From token to response

Get a token

Call v1

Generate the client

Scope