Skip to main content

​
v1.1 messaging implementation preview

  • WhatsApp text and approved-template sending through connected Meta channels.
  • Plain-text email ticket replies through configured Gmail or SMTP mailboxes.
  • Durable sending queue, idempotent acceptance, and company-scoped status lookup.
  • Separate sending permissions and dispatch-time credential, product, sender, and reply-window checks.
  • Signed Meta delivery/read updates and explicit handling of uncertain delivery.
Messaging requires the updated backend deployment and separate messaging enablement. See the sending guide.

​
v1 implementation preview

  • Company-owned bearer tokens with explicit scopes, expiry, and revocation.
  • Ticket list, retrieval, creation, and partial updates.
  • Conversation and message retrieval.
  • Sanitized WhatsApp and email channel metadata.
  • Custom ticket field definitions.
  • Bounded pagination, structured errors, company quotas, and idempotent ticket creation.
  • OpenAPI generated from Omni API endpoint metadata.
Deployment and API enablement are required before this contract becomes available on an API server. Publishing documentation does not enable API access.

​
Compatibility

The customer contract uses /api/v1. Your client should tolerate additional response fields. Breaking changes require a versioned contract and migration guidance; a general-availability support and deprecation window has not yet been published.