🌟 Describe the Feature
Currently, when using the Conversation Search API, there is no way to reliably filter or retrieve all conversations that contain call messages. The API only allows filtering by the last message type or by a general search string, which means conversations where the last message is not a call (e.g., SMS or email) are missed even if those conversations contain call messages earlier in the thread.
Secondly, when we pull messages for a conversation ID, the API returns all historical messages, not just recent or new ones. This results in unnecessary data transfer and processing. If the API allowed us to include a date parameter (such as a start or end date), we could limit the results to only messages within a specific time window, making the process much more efficient and reducing the risk of hitting rate limits.
I am requesting two features:
- That allows us to filter or search for conversations that contain at least one call message, regardless of the last message type.
- Handling messages within a specific time window.
🚀 Justification
This would help users by enabling more accurate reporting and analytics on call activity. Many workflows and integrations need to find all conversations with calls, not just those where the last message is a call. The current limitation leads to missed data and incomplete results, as conversations with calls but a different last message type are excluded.
Adding this feature would make the API much more useful for developers building call tracking, analytics, and compliance solutions.
📝 Suggestions
Introduce an API filter or endpoint that allows developers to directly retrieve all conversations containing at least one call message, regardless of the last message type. Alternatively, provide a way to filter conversations by message types present in the conversation history, not just the most recent message.
Product Area
conversations
📋 Use Case
We are importing conversations and messages from the API into Google BigQuery, which powers a Looker Studio report covering all locations. While we are able to capture location-specific data, we frequently encounter 429 "Too Many Requests" errors. This happens because, when pulling messages for a conversation ID, the API returns all historical messages, resulting in a high volume of requests and triggering rate limits. As a result, some data is missed and our reports become incomplete.
🚨 Why Should This Be Prioritized?
Client Requirement
🧠 Additional Context
No response
🌟 Describe the Feature
Currently, when using the Conversation Search API, there is no way to reliably filter or retrieve all conversations that contain call messages. The API only allows filtering by the last message type or by a general search string, which means conversations where the last message is not a call (e.g., SMS or email) are missed even if those conversations contain call messages earlier in the thread.
Secondly, when we pull messages for a conversation ID, the API returns all historical messages, not just recent or new ones. This results in unnecessary data transfer and processing. If the API allowed us to include a date parameter (such as a start or end date), we could limit the results to only messages within a specific time window, making the process much more efficient and reducing the risk of hitting rate limits.
I am requesting two features:
🚀 Justification
This would help users by enabling more accurate reporting and analytics on call activity. Many workflows and integrations need to find all conversations with calls, not just those where the last message is a call. The current limitation leads to missed data and incomplete results, as conversations with calls but a different last message type are excluded.
Adding this feature would make the API much more useful for developers building call tracking, analytics, and compliance solutions.
📝 Suggestions
Introduce an API filter or endpoint that allows developers to directly retrieve all conversations containing at least one call message, regardless of the last message type. Alternatively, provide a way to filter conversations by message types present in the conversation history, not just the most recent message.
Product Area
conversations
📋 Use Case
We are importing conversations and messages from the API into Google BigQuery, which powers a Looker Studio report covering all locations. While we are able to capture location-specific data, we frequently encounter 429 "Too Many Requests" errors. This happens because, when pulling messages for a conversation ID, the API returns all historical messages, resulting in a high volume of requests and triggering rate limits. As a result, some data is missed and our reports become incomplete.
🚨 Why Should This Be Prioritized?
Client Requirement
🧠 Additional Context
No response