Authenticate with an Intercom access token using the Authorization: Bearer header; the Data Export API uses the same auth as the rest of the Intercom API.
Initiate an export job by POSTing to /export/content/data with a JSON body specifying created_at_after and created_at_before as Unix timestamps to define the export date range.
Poll the job status by GETting /export/content/data/{job_identifier} until the status field returns complete.
Download the export file from the download_url returned in the completed job response; the file is a gzip-compressed CSV.
Parse the CSV columns: the export covers outbound content engagement data (email and in-app message sends, opens, clicks) — it does not contain full conversation transcripts or inbound user message content.
Schedule regular export jobs (e.g., daily) using the date range parameters to build an incremental pipeline; overlap the time ranges slightly to account for any delayed event ingestion on Intercom's side.
Known gotchas
The Intercom Data Export API returns outbound content engagement data only (sends, opens, clicks for messages you sent to users); it does not export full inbound conversation transcripts or user-initiated message content — use the Conversations API for that data.
The created_at_after and created_at_before date-range parameters are required; omitting them will result in an error rather than a full export.
Export files are available for download for a limited time after the job completes; download and store the file promptly — the download_url will expire and re-requesting the same date range creates a new job rather than retrieving the previous file.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp