Response Codes

Status	Meaning
`200`	Signals found. The contact exists in our database and matching signals were returned. If the contact exists but your filters (e.g. `signal_types`, `detected_after`) narrow results to zero, you will still receive a `200` with an empty `contact_signals` array — the `coverage` object will show what signal types and date ranges are available for this contact.
`404`	Contact not found. This person does not exist in our database. No credits are consumed.
`400`	Invalid request. Missing required parameters or invalid values.
`401`	Unauthorized. Invalid or missing API key.
`402`	Credits exhausted. Monthly credit limit reached.
`429`	Rate limited. Too many requests.

404 Response Example

{
  "error": "contact_not_found",
  "message": "No signals found for this contact. This person may not be in our database or may not have recent signal activity.",
  "code": 404
}

200 with Filters (no matching signals)

When the contact exists but your filters produce zero results, the coverage object tells you what IS available:

{
  "contact": { "full_name": "Jane Smith", "email": "jane@acme.com", ... },
  "company": { "name": "Acme Corp", "domain": "acme.com", ... },
  "contact_signals": [],
  "signal_summary": {},
  "total": 0,
  "coverage": {
    "total_before_filters": 24,
    "total_after_filters": 0,
    "signal_types_available": ["job-change", "linkedin-post-contact", "news"],
    "date_range": { "earliest": "2025-03-01T...", "latest": "2026-05-01T..." }
  }
}

📘
Tip: Use the coverage object to understand what signal data is available before adjusting your filters.

200Enriched contact with signals

400Invalid request parameters

401Missing or invalid authentication

404Resource not found

429Rate limit exceeded