Allow API access to all conversation parts beyond the 500-part limit

Hi Intercom Product Team,

We are currently facing a limitation when retrieving conversation data through the Intercom API. For conversations with a large number of parts, the API response does not include all conversation parts, while the missing parts are still visible in the Intercom UI.

This creates a data gap on our side, especially for analytics, reporting, auditing, and operational use cases. Since we rely on the API to ingest conversation data into our data warehouse, any missing parts can lead to incomplete or inaccurate reports.

The main challenge is the current hard limit of 500 conversation parts. We would like to request one of the following improvements:

1. Add pagination support for conversation parts.
2. Provide a dedicated endpoint to retrieve all parts for a conversation.
3. Include a cursor or next page token when a conversation has more than 500 parts.
4. Provide an export option that includes the full conversation history.

This would help ensure API data matches what is available in the Intercom UI and allow teams to build more reliable reporting and analytics.

Thank you.