Home
Guides
Start typing to search…

Quickstart

Make your first Signals API call in under 5 minutes.

Before You Start

You'll need an API key from the Autobound Portal. Once you're in, copy it from the API Keys section — it's the same key used across all Signals API endpoints.

Prefer not to write API calls directly? All of the capabilities below are also available via the Autobound MCP server, which lets AI agents and tools like Claude or Cursor access signals without any code.

Step 1: Search Signals Semantically

The search endpoint is the most powerful way to start. It accepts a natural language query — Autobound embeds it as a vector and runs a semantic search across the entire signal database to find the most relevant matches.

You can combine a query with structured filters (signal type, company size, date range, etc.) to narrow results further. Or skip query entirely and use filters alone.

curl -X POST https://signals.autobound.ai/v1/signals/search \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "companies investing in AI infrastructure",
    "signal_types": ["10k", "10q", "news"],
    "detected_after": "2026-01-01",
    "limit": 5
  }'

What to look for in the response:

  • score (0–1): semantic similarity to your query. Higher = more relevant.
  • signal_type + signal_subtype: what kind of signal this is and the specific variant
  • data.summary: a human-readable description of what the signal says
  • company.domain: use this to join signals to your CRM or account list
{
  "signals": [
    {
      "signal_id": "7dfdb4b4-c0b4-4620-aca6-e7263123028e",
      "signal_type": "10k",
      "signal_subtype": "aiInvestment",
      "signal_name": "AI & Machine Learning Investment Priority",
      "detected_at": "2026-02-14T00:00:00Z",
      "association": "company",
      "company": {
        "name": "Acme Corp",
        "domain": "acmecorp.com",
        "industries": ["Software"],
        "employee_count_low": 1001,
        "employee_count_high": 5000
      },
      "data": {
        "summary": "Acme Corp's 10-K highlights a $200M increase in AI and ML infrastructure spend.",
        "evidence": "We increased capital expenditures related to AI infrastructure by $200 million..."
      },
      "score": 0.94
    }
  ],
  "total": 1,
  "has_more": false
}

Step 2: Enrich a Company

If you already know which company you care about, use the enrich endpoint instead of search. Pass a domain (or company name / LinkedIn URL) and get back every signal we have on that company — optionally filtered by signal type and date.

This is the right call when you're loading an account page, running a pre-call brief, or triggering a workflow for a specific target account.

curl -X POST https://signals.autobound.ai/v1/companies/enrich \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "salesforce.com",
    "signal_types": ["news", "hiring-trends", "8k"],
    "detected_after": "2026-01-01",
    "limit": 20
  }'

What to look for in the response:

  • signal_summary: a count by signal type — quick way to see what's available before diving into individual signals
  • signals: the full list, sorted by detected_at descending
{
  "company": {
    "name": "Salesforce",
    "domain": "salesforce.com"
  },
  "signals": [ "..." ],
  "signal_summary": {
    "news": 12,
    "hiring-trends": 3,
    "8k": 2
  }
}

Step 3: Enrich a Contact

The contact enrich endpoint does double duty: it returns signals tied directly to that individual (job changes, LinkedIn posts, podcast appearances) and signals from their current employer — giving you a full picture of the person and the account in one call.

Pass a work email or LinkedIn URL. At least one is required.

curl -X POST https://signals.autobound.ai/v1/contacts/enrich \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "contact_email": "[email protected]",
    "signal_types": ["work-milestones", "linkedin-post-contact"],
    "include_company_signals": true,
    "limit": 20
  }'

What to look for in the response:

  • contact_signals: signals where this person is the subject (job changes, LinkedIn activity, etc.)
  • company_signals: signals about their employer (only returned if include_company_signals: true)
  • contact.title + contact.linkedin_url: resolved identity for the contact
{
  "contact": {
    "name": "Jane Doe",
    "email": "[email protected]",
    "linkedin_url": "linkedin.com/in/janedoe",
    "title": "VP of Sales"
  },
  "contact_signals": [ "..." ],
  "company_signals": [ "..." ],
  "signal_summary": {
    "work-milestones": 1,
    "linkedin-post-contact": 4
  },
  "total": 5
}

Checking Your Credit Balance

Each of the three calls above consumes 1 credit. Check your balance at any time with the free /v1/credits endpoint — no credit consumed:

curl https://signals.autobound.ai/v1/credits \
  -H "x-api-key: YOUR_API_KEY"
{
  "monthly_limit": 10000,
  "used": 3,
  "remaining": 9997,
  "period_start": "2026-03-01T00:00:00.000Z",
  "period_reset": "2026-04-01T00:00:00.000Z",
  "unlimited": false
}

Next Steps

  • Endpoint Reference — full parameter docs for every endpoint, including bulk enrichment and timelines
  • Webhooks — push signal events to your system as they're ingested
  • Signal Catalog — full list of signal type slugs and what each one contains

Updated about 7 hours ago