API reference overview

The 2mee public API lets your systems send events into 2mee and manage integration. This section is the developer reference; the Integrations guides show the same things from a setup-first angle.

Base URLs

Purpose	Base URL
REST API	https://api.2mee.com
Inbound ingest (webhooks)	https://hooks.2mee.com

Non-production stages are prefixed (e.g. https://development.api.2mee.com). Your 2mee contact will tell you which stage to use while integrating.

What’s here

• Authentication — how requests are authorised.
• The ingest API — the versioned /v1/in payload that starts or advances flows.
• Errors — the error model and what each status means.
• Rate limits — limits, quotas and 429 handling.
• REST endpoints — the generated reference, rendered from the OpenAPI spec.

These pages are a contract

Once published, the API, the ingest payload, the signing scheme and the event types are public commitments. They change by the additive-only, versioned rule — existing fields and behaviour don’t change within a version. Treat any breaking need as a new version.

Conventions

• All requests and responses are JSON (Content-Type: application/json) unless stated.
• Timestamps are ISO-8601 UTC (e.g. 2026-06-18T10:00:00Z).
• IDs are opaque strings — don’t parse them.