Skip to main content
Reports are point-in-time exports of activity data — a summary of what happened across the team (or a filtered subset of it) over a given window, delivered as an emailed file rather than rendered inline in the API response.

​
Why generation is asynchronous

Rendering a report (building the PDF/spreadsheet output) is comparatively heavy work, so it doesn’t happen inline on the request — it’s handed off to a background job, and the API call itself just confirms the job was queued. The report lands directly in the requester’s own inbox; there’s no way to redirect it to an arbitrary address, since accepting an arbitrary recipient here would turn the endpoint into a way to export an organization’s entire activity history to anyone.

​
Windows and filters

A report’s date range is always sent as explicit start/end bounds — the API doesn’t interpret phrases like “last week” itself, so whatever produced the request is responsible for resolving that into concrete dates first. Reports can be scoped by activity type, by owner, and can include a detailed row-level export alongside the aggregate summary.

​
Technical reference

For the full endpoint-by-endpoint reference, see Email an Activity Report.