What is TAMradar?
TAMradar monitors companies, contacts, and industries by tracking their online activity and sending real-time notifications when something changes.Core Concepts
- Radars — A monitor you configure. You define what to track (a company, a person, or an industry keyword) and what signal to look for (job openings, new hires, funding rounds, etc.).
- Webhooks — How you receive events. TAMradar sends a POST request to your URL when a radar fires.
- Polling — Alternative to webhooks. Use
GET /v1/updatesto pull events on your schedule. - Balance — Radars cost balance to create and run. Check yours before creating radars.
Radar Types
TAMradar has three categories of radars, each with its own creation endpoint:
Company radar types:
company_job_openings, company_new_hires, company_promotions, company_reviews, company_mentions, company_social_posts, company_social_posts_cxo, company_social_engagements
Contact radar types: contact_job_changes, contact_social_posts, contact_social_engagements
Industry radar types: industry_mentions, industry_funding_rounds, industry_new_companies, industry_job_openings
Step 1: Authentication
Every request requires your API key in thex-api-key header:
401 means your key is missing or invalid. A 200 means you’re authenticated.
Step 2: Check Your Balance
Before creating radars, confirm you have sufficient balance:?month=YYYY-MM to get stats for a specific month (defaults to current UTC month).
Step 3: Create a Radar
webhook_urlis optional. Omit it to create a poll-only radar. Updates are available viaGET /v1/updates. Add it when you want TAMradar to push events to your server in real-time.
Include recent activity with updates_since
Set updates_since to include recent activity. Choose a date a few weeks or
months back for eligible activity from that period plus ongoing updates. If
omitted, most radars start at their exact creation time, not the start of today:
even a post published one minute earlier is excluded. Your first check may return
no results, and updates may take time to arrive.
To see sample findings first, use Preview where
supported. Preview chooses its own lookback and does not accept updates_since.
- Supply an RFC 3339 timestamp with a timezone, such as
2026-07-01T09:00:00-04:00. TAMradar stores and returns the equivalent UTC instant. - The value must represent now or a past instant and may be at most five calendar years old. A five-second server tolerance exists only for clock skew; it does not enable future scheduling.
- Omit the field to store
updates_since: null. The radar’screated_atis then the effective cutoff. - Historical processing is asynchronous. Qualifying findings may continue arriving during the first 24 hours before the radar settles into its normal recent-update schedule.
2026-07-01T13:00:00.000Z.
New hires and promotions use UTC calendar-month precision: set
updates_since
to an earlier month to include activity from that month onward. If omitted,
eligibility starts in the month the radar was created.
The exact submitted timestamp is preserved in the response. During initial
engagement history, the parent post’s publication time
sets eligibility; recurring engagement delivery uses when TAMradar first
discovers the engagement.Company Radar
Monitor a company for job openings, with optional department and seniority filters:company_job_openings, company_new_hires, company_promotions, company_social_posts_cxo
Valid departments: Engineering, Sales, Marketing, Finance, Human Resources, Product Management, Operations, Customer Success, Design, Legal, Information Technology, Leadership, Research, Accounting, Administrative, Business Development, Consulting, Education, Manufacturing, Media and Communication, Project Management, Purchasing, Quality Assurance, Real Estate, Support
Valid seniorities: Owner, CXO, Vice President, Director, Manager, Senior, Entry, Training, Partner
Response (201):
radar_id. You’ll need it later.
Contact Radar
Track a specific person’s job changes or social activity:contact_job_changes— requiresdomain+ at least one of:profile_url,email,full_namecontact_social_posts/contact_social_engagements— requiresprofile_url(LinkedIn, X, or Twitter only)- For
contact_job_changes, email must identify an individual; role-based, shared, and placeholder addresses are rejected - For
contact_job_changes,profile_urlmust be a LinkedIn person profile (linkedin.com/in/...); company, school, and legacy/pub/URLs are rejected - Within the same company and radar type, duplicate matching uses email or the normalized LinkedIn profile URL;
full_nameis not a duplicate key
Industry Radar
Track a keyword or theme across companies and news:industry_mentionsandindustry_job_openings—keywordis required (min 3 chars)industry_funding_roundsandindustry_new_companies— nokeywordneededcountries— optional forindustry_job_openings(job location) andindustry_funding_rounds(company headquarters country), max 5. Two-letter codes or country names (e.g.US,United Kingdom); saved and returned as the country namerounds— optional forindustry_funding_roundsonly. Exact round labels (e.g.Seed,Series A), each oncecountriesorroundson a radar type that doesn’t use them returns400
Step 4: List and Inspect Radars
Response (200, with
limit=1):
has_more is true, repeat the same filters and pass next_cursor as
the cursor query parameter. The final page returns has_more: false and
next_cursor: null. The count value applies only to the current page.
Unknown query parameters return 400; use cursor, not next_cursor, in the
request.
For recovery or reconciliation, follow every cursor to complete the traversal
and compare it with your local radar inventory. If radars may have been created
while you were paging, start a fresh request without a cursor to pick them up.
This lists radar records; use GET /v1/updates for findings and failures.
Note: Filter fields (departments, seniorities, job_titles) and identifier fields (profile_url, email, full_name, keyword) are returned flat at the top level of each radar object. They are only present when set.
Step 5: Receive Events
When a radar fires, TAMradar POSTs an event to yourwebhook_url.
Webhook Payload Structure
All webhook events follow this envelope:data— radar context (always present, same fields regardless of type)content— the actual finding (structure varies byradar_type)
Your Webhook Must
- Accept
POSTwith a JSON body - Return any
2xxstatus code within a reasonable timeout - Handle duplicates — use
update_idas an idempotency key
Polling Alternative
If you prefer pull over push, useGET /v1/updates:
radar_id (comma-sep, max 10), radar_type (comma-sep), domain (comma-sep, max 10), since (ISO 8601), cursor, limit (1–100, default 25), update_type (radar_finding | radar_failure, default: radar_finding)
updates_since and the polling query parameter since serve different
purposes. Radar updates_since is the permanent eligibility boundary selected
at creation. GET /v1/updates?since= only filters TAMradar updates that have
already been created; it does not change the radar.
Response shape:
next_cursor as cursor in the next request to paginate, and repeat the same since and filters — the cursor does not remember them. has_more: false means you’ve reached the end.
Step 6: Bulk Create Radars
Submit a bulk request for asynchronous processing (up to 1000 items):webhook_urlis required at the envelope level for async bulk- Items can mix company, contact, and industry types
- Max 1000 items, max 1MB request body
- Item-level validation and creation happen asynchronously after submission
202 Accepted):
bulk_id, then poll for status:
status: "processing"while items are still runningstatus: "completed"when all items are terminal- Per-item outcomes in
radars[]withitem_indexmapping back to the input order radars[].update_idas the per-item correlation key (radar_created/radar_failure)
- Use top-level
update_idonbulk_completedto deduplicate the batch event itself - Use
radars[].update_idinsidebulk_completedto map each item back to its individual item event
Step 7: Deactivate a Radar
Error Responses
All errors follow the same structure:
Use
error_id when contacting support. It traces the exact request in our logs.