POST to /export/content/data with a JSON body containing 'created_at_after' and 'created_at_before' as Unix timestamps, and 'export_type': 'conversations' (or 'contacts', 'companies', 'events', etc.).
The response contains a 'job_identifier' and 'status'; poll GET /export/content/data/{job_identifier} until 'status' is 'complete'.
When status is 'complete', the response contains a 'download_url' — fetch this URL to download a gzip-compressed CSV or NDJSON file; the URL is time-limited.
Decompress and parse the export file; large exports may be split into multiple files referenced in a 'data' array within the response.
Export jobs have a maximum time window (typically 30 days per request); for longer date ranges, make multiple overlapping export requests.
Store the download before the URL expires; re-requesting an export for the same period requires a new job submission.
Known gotchas
Export jobs can take several minutes to hours for large workspaces — implement robust polling with a generous timeout and store the job_identifier persistently in case your process restarts.
The download URL is pre-signed and expires after a short window (typically a few hours); failure to download within that window requires resubmitting the export job.
Intercom export data does not include real-time data — there may be a lag of several hours between conversation events and their availability in the export.
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