Helpers

Tech Intent Search Results

Poll a tech intent-search job and page through its results. Submit a job first via POST /api/v2/tech/companies/intent-search (“Search Companies by Tech Stack with Intent”, under Company Search), which returns a job_id.

No API key yet? Sign up via Agent Auth to get your X-API-Key - the only required header for this endpoint.

This single endpoint returns both the job status (pending → running → completed / failed), a manifest summary once complete, and one page of result rows. Walk pages by passing the returned next_cursor as ?cursor=.

Check status for completion - not next_cursor. A still-running job can return a null next_cursor simply because later pages haven’t been written yet; only status: "completed" means the full result set is available.

Each row is a company hit (same shape as Search Companies By Tech Stack, with firmographics when enrichment ran) plus an intent block: the verified activity, an LLM reason quoting the exact posting phrases that support the verdict, and the qualified_job itself. The manifest also reports companies_scanned vs companies_qualified so you can see how selective your activity was.

No credits are charged for polling - the job’s credits are billed once, when it completes.

GET

api

tech

companies

intent-search

{job_id}

Poll results

# first page (also shows status)
curl -sS "https://api.openfunnel.dev/api/v2/tech/companies/intent-search/JOB_ID" \
  -H "X-API-Key: YOUR_API_KEY"

# next page
curl -sS "https://api.openfunnel.dev/api/v2/tech/companies/intent-search/JOB_ID?cursor=page_0001" \
  -H "X-API-Key: YOUR_API_KEY"

{
  "job_id": "8bda2224-3772-4430-94d3-69a526872227",
  "status": "completed",
  "manifest": {
    "pages": 1,
    "page_size": 100,
    "count": 50,
    "partial": false,
    "tech": "Snowflake",
    "activity": "migrating off Redshift to Snowflake",
    "companies_scanned": 230,
    "companies_skipped_no_evidence": 4,
    "companies_qualified": 50,
    "total_companies_matched": 8412,
    "credits_consumed": 500
  },
  "error_message": null,
  "rows": [
    {
      "company_slug": "acme-analytics",
      "company_name": "Acme Analytics",
      "post_count": 7,
      "first_posted_at": "2026-02-11T09:30:00Z",
      "last_posted_at": "2026-05-28T17:05:00Z",
      "enriched": true,
      "website": "acme-analytics.com",
      "linkedin_url": "https://www.linkedin.com/company/acme-analytics",
      "employee_count": 850,
      "hq_country_code": "USA",
      "funding_stage": "Series C",
      "intent": {
        "activity": "migrating off Redshift to Snowflake",
        "reason": "The posting describes \"leading our migration from Redshift to Snowflake\" as a core responsibility of the role.",
        "qualified_job": {
          "title": "Senior Data Engineer",
          "url": "https://www.linkedin.com/jobs/view/4012345678",
          "created": "2026-05-28T17:05:00Z",
          "snippet": "…experience leading our migration from Redshift to <em>Snowflake</em>…"
        }
      }
    }
  ],
  "page": "page_0000",
  "next_cursor": null,
  "count": 50
}

Headers

X-API-Key

string

required

Path Parameters

job_id

string

required

The job_id returned by the intent-search submit endpoint.

Query Parameters

cursor

string | null

Page to read, e.g. page_0001 (use the next_cursor from the previous response). Omit for the first page.

Response

Job status, manifest, and one page of results.

Combined job status + one page of results. Check status for completion (not next_cursor), and walk pages with next_cursor.

job_id

string

required

status

string

required

pending, running, completed, or failed.

manifest

TechIntentManifest · object

Job summary; populated once the job completes.

Show child attributes

error_message

string | null

Failure reason when status is failed.

rows

TechIntentCompanyRow · object[]

Qualified companies in the requested page.

Show child attributes

page

string | null

Name of the page returned, e.g. page_0000.

next_cursor

string | null

Pass as ?cursor= to fetch the next page; null on the last available page.

count

integer

default:0

Number of rows in this page.

Cancel Bulk Lookalike JobCancel a running or pending bulk lookalike job. Submit a job first via **`POST /api/v1/account/search-lookalikes-bulk`** ("Search Lookalikes Bulk", under Company Search), which returns a `job_id`. <Info>**No API key yet?** [Sign up via Agent Auth](/agent-auth/agent-auth/agent-sign-up) to get your `X-API-Key` - the only required header for this endpoint.</Info> The job moves to a transient `cancelling` state and stops at its next checkpoint. Whatever pages were already produced are kept and remain readable via the poll endpoint, and you are charged **only for the companies actually delivered** before the cancel - nothing for the abandoned remainder. The job then settles to a terminal `cancelled` status. Returns **409** if the job has already finished (`completed` / `failed` / `cancelled`), and **404** if no job with that id exists for your API key. Poll **`GET /api/v1/account/search-lookalikes-bulk/{job_id}`** for the final `cancelled` state and the partial results. ## When to cancel Cancel when finishing the job is no longer worth it - e.g. you requested a large `limit` but already have enough companies from the pages delivered so far, the query turned out too broad, or you simply want to stop spend. Because credits are billed **only for companies actually delivered** before the cancel (never the abandoned remainder), cancelling early is how you cap credit usage on an over-scoped job.

⌘I

Poll results

# first page (also shows status)
curl -sS "https://api.openfunnel.dev/api/v2/tech/companies/intent-search/JOB_ID" \
  -H "X-API-Key: YOUR_API_KEY"

# next page
curl -sS "https://api.openfunnel.dev/api/v2/tech/companies/intent-search/JOB_ID?cursor=page_0001" \
  -H "X-API-Key: YOUR_API_KEY"

{
  "job_id": "8bda2224-3772-4430-94d3-69a526872227",
  "status": "completed",
  "manifest": {
    "pages": 1,
    "page_size": 100,
    "count": 50,
    "partial": false,
    "tech": "Snowflake",
    "activity": "migrating off Redshift to Snowflake",
    "companies_scanned": 230,
    "companies_skipped_no_evidence": 4,
    "companies_qualified": 50,
    "total_companies_matched": 8412,
    "credits_consumed": 500
  },
  "error_message": null,
  "rows": [
    {
      "company_slug": "acme-analytics",
      "company_name": "Acme Analytics",
      "post_count": 7,
      "first_posted_at": "2026-02-11T09:30:00Z",
      "last_posted_at": "2026-05-28T17:05:00Z",
      "enriched": true,
      "website": "acme-analytics.com",
      "linkedin_url": "https://www.linkedin.com/company/acme-analytics",
      "employee_count": 850,
      "hq_country_code": "USA",
      "funding_stage": "Series C",
      "intent": {
        "activity": "migrating off Redshift to Snowflake",
        "reason": "The posting describes \"leading our migration from Redshift to Snowflake\" as a core responsibility of the role.",
        "qualified_job": {
          "title": "Senior Data Engineer",
          "url": "https://www.linkedin.com/jobs/view/4012345678",
          "created": "2026-05-28T17:05:00Z",
          "snippet": "…experience leading our migration from Redshift to <em>Snowflake</em>…"
        }
      }
    }
  ],
  "page": "page_0000",
  "next_cursor": null,
  "count": 50
}