The activity timeline, space-scoped, newest first.
Filters: space_id (required to return anything), contact_id / business_id / deal_id / record_id to anchor to one record, type, and the shared created_after / created_before window -- applied to occurred_at, because a timeline is asked about when things HAPPENED, not when the row was written.
Private logged emails are filtered per-viewer by services.activity, the same rule the browser timeline uses; an API caller must not see through it.
URL
- User APIhttps://sales.mattering.io/api/user/v1/activities/
- Service tierhttps://sales.mattering.io/api/internal/activities/
Query parameters
| Name | Default |
|---|---|
created_after | none |
created_before | none |
fields | none |
space_id | none |
type | none |
view | none |
Pagination
Accepts limit and offset; the default page is 100 and the server caps limit at 500. The response meta carries total, returned, has_more and next_offset.
Responses
200 data and meta envelope, legacy keys repeated beside data
{
"data": {
"activities": "..."
},
"meta": {
"total": 0,
"limit": 0,
"offset": 0,
"returned": 0,
"has_more": true,
"next_offset": 0
}
}
Field names come from the code; values are placeholders (... is a string, 0 a number, dates are ISO 8601).
Errors
| Status | Code |
|---|---|
| 401 | unauthorized |
Example
curl -X GET "https://sales.mattering.io/api/user/v1/activities/?created_after=...&created_before=...&fields=..." \ -H "Authorization: Bearer $MATTERING_API_KEY"
curl -X GET "https://sales.mattering.io/api/internal/activities/?created_after=...&created_before=...&fields=..." \ -H "X-Internal-Secret: $MATTERING_INTERNAL_API_SECRET" \ -H "X-Internal-Org-Id: $ORG_ID" \ -H "X-Internal-User-Email: you@example.com"
Source: CRMCore/internal_api.py (internal_api.activities)