Skip to main content
Messaging endpoints are read-only in Public API v1. They expose chat and message DTOs for integrations that need conversation context, without unread-state internals, push tokens, participant auth fields, raw media URLs, moderation state, or delivery provider payloads. The authenticated company is always derived from the Bearer token. Requests must not include companyId.

Scopes

List client chats

Required scope: messages:read Validation: Response fields: Not exposed: participant email, device tokens, unread counters, muted states, deletion markers, role permissions, or raw participant documents.

List chat messages

Required scope: messages:read Validation: Response fields: Not exposed: raw attachment URLs, storage keys, upload metadata, push delivery state, read receipts, internal moderation fields, deleted-message audit data, provider payloads, or staff-only support context.

Rate limits

Messaging endpoints use the standard Public API client rate limit: 10 requests per second per OAuth client. Responses include the standard RateLimit-* and X-RateLimit-* headers documented in Contracts.