Activity
Get Activity
GET
Retrieve the full details of a specific activity record, including the complete original request parameters and the entity IDs that were returned. Use the
The full activity record.
The full, unmodified request body that was sent to the original endpoint. This is the complete version of what
For enrichment types, this is the enrichment request:
The entity IDs that were captured for this activity response. Search activities only include the IDs returned by that specific API response page, so a search originally requested with
activity_id from Search Activity results.
Path Parameters
The activity ID to retrieve (e.g.,
act_r7s8t9u0).Query Parameters
Page number for the
entity_ids array. Since a single search can return thousands of entities,
the IDs are paginated separately.Entity IDs per page (min:
1, max: 250).Response Fields
data
The full activity record.
| Field | Type | Description |
|---|---|---|
activity_id | string | Unique activity identifier |
type | string | Activity type. See Activity Types. |
created_at | string | ISO 8601 timestamp of when the request was made |
request | object | The complete original request parameters (see below) |
result_summary | object | Full result and credit breakdown (see below) |
entity_ids | object | Paginated entity IDs returned by this activity (see below) |
request
The full, unmodified request body that was sent to the original endpoint. This is the complete version of what request_summary shows in Search Activity.
For search types, this is the exact search request body:
| Field | Type | Description |
|---|---|---|
locations | array | Location objects used |
filters | array | Filter objects with filter_id, operator, value |
fields | string[] | Requested field IDs |
property_match | string | Person-to-property relationship (if set) |
page | integer | Page number requested |
per_page | integer | Results per page |
sort | array | Sort configuration |
| Field | Type | Description |
|---|---|---|
enrichment_type | string | The enrichment method |
items | array | The input items submitted (email addresses, phone numbers, addresses, etc.) |
fields | string[] | Requested field IDs |
include_properties | boolean | Whether properties were included |
The
request object contains the exact parameters you can copy-paste to re-run the same query.
For search types, pass it directly to the corresponding search endpoint. For enrichment types,
wrap the items array back into a data field.result_summary
| Field | Type | Description |
|---|---|---|
total_results | integer | Total matching records |
total_pages | integer | Total pages available (search types only) |
pages_retrieved | integer | Pages you actually fetched (search types only) |
items_submitted | integer | Items in the request (enrichment types only) |
items_matched | integer | Items that matched (enrichment types only) |
items_unmatched | integer | Items that didn’t match (enrichment types only) |
credits_used | integer | Total credits consumed |
credits_breakdown | object | Breakdown of credit charges |
credits_breakdown.new_people | integer | New people accessed (charged) |
credits_breakdown.new_properties | integer | New properties accessed (charged) |
credits_breakdown.repeat | integer | Previously accessed entities (free) |
entity_count.people | integer | Unique people returned |
entity_count.properties | integer | Unique properties returned |
entity_ids
The entity IDs that were captured for this activity response. Search activities only include the IDs returned by that specific API response page, so a search originally requested with per_page: 25 will only have up to 25 entity IDs in its activity detail. When an activity captured more IDs, they are paginated with the entity_page and entity_per_page query parameters.
| Field | Type | Description |
|---|---|---|
people | string[] | Array of dm_person_id values (e.g., "per_x1y2z3") |
properties | string[] | Array of dm_property_id values (e.g., "prop_a1b2c3") |
pagination.page | integer | Current entity page |
pagination.per_page | integer | Entity IDs per page |
pagination.total_people | integer | Total unique people across all pages |
pagination.total_properties | integer | Total unique properties across all pages |
pagination.has_next_page | boolean | Whether more entity IDs exist |
Paginating Entity IDs
A single activity can capture up to the number of records returned by the original request. Theentity_ids section paginates those captured IDs separately so the activity detail response stays fast.
To retrieve all entity IDs from a large search:
Re-Running a Past Search
Therequest object contains everything you need to replay a search:
Re-running a search within the same billing period will not charge credits for entities you’ve
already accessed. Check
credits.breakdown.repeat in the search response to see how many were
free.Notes
- This endpoint does not consume credits.
- Activity is scoped to your organization — you can access activity created by any API key under your account.
- Count activities (
count_people,count_properties) will have emptyentity_idssince no entity data is returned. - For enrichment activities,
entity_idsincludes only the entities from matched items. - The
request.itemsarray in enrichment activities is capped at the first 100 items in the response. For enrichments with more than 100 items, the full list is available but truncated in this view. - Activity records are retained for 12 months.