mySDRDocs

API reference

Technology

Companies that use or just adopted a tool.

View Markdown

In the API this is the signal type tech_adoption (Companies using a technology). You run it with the same route as every signal: a search.

What it finds

Companies that use one of your technologies, seen in their job postings, with the evidence per company: when the technology was first and last seen, how sure the match is and in how many job posts. Only companies where the technology was seen in the last 12 months, with medium or high confidence. Turn the companies into people with POST /v1/leads.

Rows and price

  • One row per company, as the source shows it, with no AI judging it: you decide which rows fit.
  • At most 25 rows per search, 10 unless you send limit; more with cursor. 3 credits per row.
  • A search that delivers nothing is free.

The signal object

Send it as signal in the body of POST /searches. The other fields of the body are on Start a search.

  • type string · required — Always tech_adoption.
  • technologies string[] · required — Technology slugs, e.g. hubspot or salesforce; a company that uses any of them matches. An unknown slug is a 400 (code unknown_technology) that lists the closest known slugs. 1 to 5 items.
  • countries string[] — Countries of the company (ISO 3166-1 alpha-2; UK is accepted for GB). Empty or missing = any country. Up to 20 items.
  • company_sizes string[] — Headcount ranges of the company; empty or missing = any size. One of: self-employed, 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+.
  • exclude_domains string[] — Companies you already have, as domains (a website URL or an email address works too). They are never fetched or charged. Up to 100 items.

Limits

  • Evidence comes from job postings: a company that uses a tool without hiring for it is not seen.
  • A company counts only when the technology was in a job post of the last 12 months, with medium or high confidence: older or weaker evidence is left out, at no charge.
  • Each row is expensive to fetch, so a search fetches exactly limit companies; get more with next_cursor.
  • Companies fetched for the same technology in the last 30 days come from our cache.

Run it

  • Once: Start a search (POST /searches). Preview a search shows the most it can cost first. The rows are in List search results.
  • To follow it: run the search again, for example every week. There are no watches.
  • From companies to people: Find people at companies (POST /leads) turns the companies into the people you sell to.
  • From your assistant: the Signals MCP server (MCP) runs it with search_signals.

Example

A search, POST /searches:

{
  "signal": {
    "type": "tech_adoption",
    "technologies": [
      "hubspot"
    ],
    "countries": [
      "BE",
      "NL"
    ]
  },
  "limit": 10
}