Signals

Scan Company For Signals

Watch the company (pinned) and check it in the next scan batch (202). Its careers, pricing and about pages are re-crawled politely with conditional GETs. 404 for a missing company, 422 when it has no domain.

API key access

Needs the leads:write scope with an API key (ro_pat_...). A signed-in session uses the caller's role.
POST/api/v1/signals/scan
AuthorizationBearer <token>

Access token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).

In: header

Header Parameters

X-Workspace-Id?string | null

Id of the workspace to act on (must be a member).

company_idstring
Formatuuid

Response Body

curl -X POST "http://localhost:8000/api/v1/signals/scan" \  -H "X-Workspace-Id: string" \  -H "Content-Type: application/json" \  -d '{    "company_id": "b2e6a1c3-1a5e-44ae-a8fd-81f76fd715cf"  }'
{
  "company_id": "b2e6a1c3-1a5e-44ae-a8fd-81f76fd715cf",
  "pinned": true,
  "next_check_at": "2019-08-24T14:15:22Z",
  "last_checked_at": "2019-08-24T14:15:22Z"
}
Empty
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string",
      "input": null,
      "ctx": {}
    }
  ]
}