Create Ticket External Messages
Register Serval messages as already present in an external channel. This records external message links so the egresser will not re-send those messages to the external system. Use this after posting a summary of prior conversation to an external ticket to prevent the individual historical messages from being replayed. Pass a single message to register one, or many to register in bulk.
Authentication and permissions
Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The Serval ticket the messages belong to.
Body
The channel the messages should be registered against. Resolves to the same source the egresser uses to decide what to sync.
The messages to register as already present in the external channel. Provide one for a single registration or many for a bulk registration.
Response
Success
The external message links that were created or updated.

