We sell high tickets and our bottleneck today is to combine what happens in the DMs with what happens in sales. We do all this reconciliation by hand, exporting and crossing data, which wastes time and working with outdated information. What we need is to be able to read the ZeroChats data from outside and dump it into our system to have a single view of marketing and sales. Data we need per conversation: Conversation ID and Contact ID (Instagram user) Date and time of the start and of the last message Conversation status (active, qualified, discarded, scheduled) Exact source of the lead: story, post, reel, announcement, link in bio, direct DM. Ideally with the ID of the specific content that generated it, and with the UTM parameters when they exist Qualification answers given by the lead Full transcript of the conversation With that, we can calculate conversion rate per channel and per piece of content ourselves, so there's no need for the API to provide aggregated metrics, although a summary endpoint would be useful. How we would use it, in order of priority: A read-only REST endpoint for conversations and contacts, with date range filtering, pagination and API key authentication. With this we already covered 80% of the problem because we can synchronize every night. Webhooks that trigger key events (conversation started, qualified lead, converted lead). This is what would allow us to react hot instead of waiting for the batch. A scheduled CSV export, if the full API falls far in the roadmap. It would be an acceptable patch in the meantime. I await your answer We are active users and are willing to beta test the API and give them detailed feedback on data structure and real use cases before the public release. From Sebastian Nájera's team Cristopher Gonzalez Growth Operator