API changes

This log is for platform developers: new functionality, behavioral fixes and required integration updates. Internal development history preceding the first stable contract is preserved in the repository archive; it is not a list of supported public API versions. Cosmetic website changes do not belong here.

1.0.0 — first stable public contract

The first stable version brings the existing network functionality into one documented contract. /v1/... paths, keys and business request/event payloads are retained; no registration or data migration is required. GET /v1/capabilities declares protocol_version: "1.0.0". Check your environment’s deployed version and required capabilities before use.

• Membership and profiles. Explicit consent, profile synchronization, your own external_id values, test/live environments, hiding, erasure and account restoration under the documented rules.
• Discovery. Filtered feeds/search with cursors, ordinary likes, dislikes, incoming likes and matches. Match lifetime is not a commercial service.
• Chat and events. Messages with optional translation and original-text fallback, read receipts and history; signed webhooks or polling, durable message retries and handling of late events/erasures.
• Safety. Moderation, photo checks, reports, blocks, retention and platform isolation. Capabilities describe configuration, not external AI health.
• Optional services. Boost, superlike, incognito and rewind all start at zero price. Live RUB checkout is isolated from TEST credits. Spending-account enrollment is explicit; existing integrations retain legacy behavior until then.
• Initial release limitations. Production video is disabled; calls are unavailable. Positive RUB payments, automated bonus issuance and commerce actions through MCP are not provided yet. Basic MCP tools remain available; the MCP protocol version stays 2024-11-05.

See the API reference for fields/errors and optional services for their terms.

Reading future versions

• 1.0.1: backward-compatible fix.
• 1.1.0: backward-compatible addition.
• 2.0.0: incompatible contract with a separate migration plan. We give platforms at least 60 days’ notice of breaking changes and maintain the previous version during that period.

Site release versions are independent of the API version. A feature must be available in your environment even if already documented.