Manage decoy contacts from your own stack.
Ditch manual CSV exports. The Contacts API plugs seeding into your automated workflows, web forms, and databases for real-time leak detection — no human in the loop required.
Why automate seeding at all?
Manual decoy placement works fine at low volume and stops scaling the moment a partner program, a form, or a database grows past what one analyst can seed by hand. The API brings decoy-contact management into your developer ecosystem instead — automated lead monitoring, dynamic CRM seeding, and compliance verification without someone copying addresses into a spreadsheet.
Zero manual exports
Pull and deploy synthetic contacts programmatically, on your own schedule.
Pinpoint alert accuracy
Every contact is paired with its exact deployment location, so an alert tells you precisely where to look.
Continuous monitoring
Run background scripts that seed and test systems 24/7, not just when someone remembers to.
What teams build with it
Automated web-form seeding
Fetch a fresh contact, auto-populate a lead-capture form, and report the submission URL back via the API — your forms stay live and tracked without a human copying addresses by hand.
Lead-gen & partner monitoring
Embed seeds directly into automated partner submission channels so every batch you send downstream is independently auditable, not just the ones someone remembered to check.
Decoy data insertion (honeytokens)
Run scheduled scripts that plant seeds as honeytokens inside CRMs, call centers, or internal databases to catch insider threats and unauthorized distribution the moment it happens.
How it works
Order your inventory
Generate and order fresh synthetic contact batches directly inside Assumed — the same inventory the dashboard and Chrome extension draw from.
Fetch unused contacts
Your application calls GET /api/v1/contacts?used=0 to retrieve available contacts from your active inventory.
Seed your systems
Your scripts, test bots, or internal tools plant the retrieved contact into a form, partner portal, or database — anywhere a real lead would end up.
Tag & track
PUT /contact/{id} reports back the exact placement and marks the contact used. Any future inbound call, text, or email ties straight back to that location.
Sample usage
Every request is authenticated with an API key passed as a header. Fetch unused contacts from your active inventory:
Once a contact is placed, report back where — this is the only write endpoint, and it's what ties a future inbound contact to a specific placement:
Boolean filters and fields (like used) take 1/0, not true/false. Always send Accept: application/json.
API access is issued per account, not self-serve signup.
Every account can order and plant seeds manually or through the Chrome extension right away. To automate it, contact our engineering support team with your account email and the integration you're building — we'll issue a key and send over full endpoint references, payload examples, and auth details.