Message Collection API
Multiple access controls based on provided filters:
provider_idUser must be a direct member of provider organization (1) to access provider-only messages š
customer_idUser must be a direct member of customer organization (1) to access customer-only messages š
thread_idšØ Gate errors: You must filter by "provider_id" or "customer_id" along with "thread_id" to establish organizational context.
provider_id, customer_idAt least one of the following conditions must be met:
provider_id, thread_idThread ID 1 must belong to provider organization (1) š
customer_id, thread_idUser must be a direct member of customer organization (1) to access customer-only messages š
Thread ID 1 must belong to customer organization (1) š
provider_id, customer_id, thread_idAt least one of the following conditions must be met:
Thread ID 1 must belong to provider (1) and customer (1) organizations š
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Authorization: Bearer <token> header is required for authorization, requests without a valid and active authorization header will be denied access with a 401 Not Authorized HTTP status code.
Query param filters, URL encoded JSON object with fields: archived_at, bot_id, conversation_id, customer_id, data, id, thread_id, message, provider_id, reference_0_id, reference_0_type, timestamp, user_id, trace_id
Example:
/api/messages?filters={"bot_id": ..., "conversation_id": ..., "customer_id": ..., "data": ..., "thread_id": ..., "message": ..., "provider_id": ..., "reference_0_id": ..., "reference_0_type": ..., "timestamp": ..., "user_id": ..., "trace_id": ...}Successful response
The response is of type object.