The customer activation platform.Every interaction becomes a qualified contact. Book a demo

Changelog

Check the current status of the public API changelog and the safest way to monitor integration-impacting changes today.

A full public, reverse-chronological API changelog is not published in this help center yet.

What to rely on today

  • Versioned endpoint paths and webhook event names
  • Staging validation before every production rollout
  • Direct communication from OmniLab for tenant-specific integration changes
  • Your own monitoring for authentication failures, schema drift, and webhook delivery errors
  • Alert on repeated 401 or 403 responses from approved API endpoints.
  • Alert on webhook signature verification failures.
  • Track repeated 410 Gone, 429, or 5xx delivery outcomes on your receivers.
  • Keep sample staging payloads so you can detect schema changes quickly.
  • Re-run end-to-end tests before large launches or major tenant reconfiguration.

Do not wait for production traffic to tell you something changed

Because the public changelog is still maturing, staging tests and good observability are the safest way to catch integration-impacting changes early.

Versioning strategy

See where version markers appear in the currently documented surface.

Rate limits

Build client-side safety even before a full changelog exists.

About webhooks

Monitor signed delivery behavior and retries carefully.

Was this helpful?

Optional comments help us improve this page for future authors and readers.

On this page

What to rely on todayRecommended monitoring checklistRelated