Thread Collection API
Multiple access controls based on provided filters:
conversation_id, provider_idUser must be a direct member of provider organization (1) to access provider-only threads 🔐
Conversation ID 1 must belong to provider organization (1) 🔐
conversation_id, customer_idUser must be a direct member of customer organization (1) to access customer-only threads 🔐
Conversation ID 1 must belong to customer organization (1) 🔐
provider_idcustomer_idUser must be a direct member of customer organization (1) to list customer-only threads 🔐
conversation_id, provider_id, customer_idAt least one of the following conditions must be met:
Conversation ID 1 must belong to provider (1) and customer (1) organizations 🔐
provider_id, customer_idAt least one of the following conditions must be met:
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, conversation_id, created_at, customer_id, id, parent_message_id, parent_thread_id, provider_id, title, updated_at, user_id
Example:
/api/threads?filters={"conversation_id": ..., "customer_id": ..., "parent_message_id": ..., "parent_thread_id": ..., "provider_id": ..., "title": ..., "user_id": ...}Successful response
The response is of type object.