Why Activity Matters
Every time you run a search or enrichment through the API, DealMachine logs it as an activity record. Each record captures:- What you requested — the full parameters (locations, filters, enrichment inputs)
- What came back — summary stats and the entity IDs returned
- What it cost — credits consumed, broken down by new vs. repeat
- “What searches have I run this month?”
- “Have I already looked up this property or person?”
- “Which of my searches used an equity filter?”
- “Did I already enrich john@example.com?”
- “What were the exact filters I used in that search last week?”
- “Which entity IDs came back from a specific request?”
Activity Types
Every activity has atype that tells you which endpoint generated it:
| Type | Endpoint | Description |
|---|---|---|
search_people | POST /v1/people/search | People/contact search |
search_properties | POST /v1/properties/search | Property search |
count_people | POST /v1/people/search/count | People count query |
count_properties | POST /v1/properties/search/count | Property count query |
enrich_email | POST /v1/enrichment/email | Email enrichment |
enrich_phone | POST /v1/enrichment/phone | Phone enrichment |
enrich_address | POST /v1/enrichment/address | Address enrichment |
enrich_latlng | POST /v1/enrichment/latlng | Lat/lng enrichment |
enrich_apn | POST /v1/enrichment/apn | APN enrichment |
Common Workflows
Searching by Text
Use thequery parameter to search across all your activity by filter name, location, enrichment input, or anything else in the original request. This is the fastest way to find a past search when you remember what you searched for but not when.
equity_percent filter. The response includes a matched_on array showing exactly which part matched. See Text Search for the full reference.
Reviewing Past Searches
Pull up everything you’ve searched in the last 30 days:Checking If You’ve Already Accessed an Entity
Before running a new search or enrichment, check if you’ve already pulled data on a specific person or property:Replaying a Search
Found an activity record for a search you want to re-run? The Get Activity endpoint returns the full original request parameters, so you can copy them directly into a new search request.Building a Local Cache
Use activity history to maintain a local record of which entities you’ve already pulled. Page through theentity_ids on each activity to build a local lookup table, then skip entities you already have when running new searches.
Activity Endpoints
| Endpoint | Method | Description |
|---|---|---|
/v1/activity/search | POST | Query and filter your activity history |
/v1/activity/:activity_id | GET | Get full details of a specific activity record |
Notes
- Activity records are read-only. You cannot modify or delete them.
- Activity is scoped to your organization — all API keys and OAuth tokens under the same organization share the same activity log.
- Count queries (
count_people,count_properties) are logged but do not include entity IDs since no data is returned. - Activity records are retained for 12 months from the date of the request.
- Querying activity does not consume credits.
Related Guides
Search Activity
Query and filter your activity history.
Get Activity
Get full details of a specific activity record.
Searching
How to run searches that generate activity.
Credits
How credits work and how activity tracking helps avoid duplicates.