Changelog & status

This is the public record of changes to the parts of 2mee you build against — the API, the ingest contract, the signing scheme and the event types.

Versioning

The public API and contracts change by the additive-only, versioned rule. Additive changes (new endpoints, new optional fields, new event types) don’t bump the version. Breaking changes ship as a new version with a deprecation window for the old one.

Unreleased

• Docs site launched. First public release of the 2mee documentation site, covering concepts, portal guides, the API and webhooks reference, and integration guides.
• Ingest contract v1 published as the canonical inbound payload — see the ingest API.
• Segment integration documented (generic webhook method), inbound and outbound — see Connect Segment.

How deprecations work

When something is deprecated:

1. It’s announced here with the replacement and a removal date.
2. Both old and new keep working through the deprecation window.
3. After the window, the old behaviour is removed.

Subscribe to your account’s update channel (ask your 2mee contact) to be notified of API-affecting changes ahead of time.