Report a check of your own signal

Each hit is a line on the Activity tab (type signal_hit) and puts the signal in the Signals and Last signal columns of the row; it changes nothing about where the row stands. Someone not in Leads or Companies yet is added, with the signal as note; a lead from the user's own signals (a number) gets your own row behind it. Report what is new since your last check, with external_id (e.g. the URL of what you saw): a hit with an external_id this signal already reported counts once (duplicate). Each hit goes on its own: one that fails (ok: false, with the error) does not stop the others. A value that is wrong without looking anything up (no summary, a source that is not a web address, both lead and company) refuses the whole call, and nothing changes. A paused signal takes no checks (409).

A signal your agent runs itself, with its own tools: hiring spikes on careers pages, posts on X, a newsletter, a list in the CRM. Register it and the user sees it on the Signals page of mySDR, next to the signals mySDR runs: what it watches, where, how often, when you last checked and what it caught. mySDR does not run, schedule or check it: it shows what you report. These routes are the tools save_agent_signal, log_signal_hits, list_agent_signals and delete_agent_signal of the assistant server.

Authentication

Send Authorization: Bearer gtk_…. Create the key under Connect assistant → API keys. Every gtk_ key can call these routes, also while the Signals API is closed. A missing, invalid or revoked key is 401.

Path parameters

• key string · required — The key of your signal (hiring_spike).

Body parameters

• checked_at string — When you checked: an ISO time or a date; default now. A time in the future counts as now.
• next_check_at string | null — When you check next; null clears it.
• note string | null — What this check did ("140 careers pages, 3 spikes"), up to 500 characters.
• hits object[] — What it caught, up to 100; leave it out or empty when it caught nothing.
• hits[].lead string | object — The person, as POST /outreach/activity takes one: a row id (a number, sav_…, per_…), a LinkedIn URL or an address, or { "linkedin_url", "name", "title", "company", "company_domain", "email" } for someone not in the table yet.
• hits[].company string | object — Or the company: sav_…, cmp_…, its domain, LinkedIn page or name, or { "name", "domain", "linkedin_url" }.
• hits[].summary string · required — What you saw, up to 1000 characters (e.g. "12 open roles on the careers page, up from 3").
• hits[].source_url string — Where you saw it (https://…, up to 1000 characters).
• hits[].occurred_at string — When it happened: an ISO time or a date; default checked_at.
• hits[].external_id string — Your own id of what you saw (its URL, a post id), up to 200 characters: the same one again counts once.

Response

• object string · required — Always agent_signal_check. One of: agent_signal_check.
• signal object · required — The signal after this check, as GET /agent-signals/{key} gives it.
• recorded integer · required — New hits.
• duplicates integer · required — Hits this signal had reported already (the same external_id).
• failed integer · required — Hits that could not be recorded.
• added_to_table integer · required — People and companies that were not in the tables yet.
• results object[] · required — Per hit, in order: index, ok, and id (the line in the log), duplicate, row (id, object, name) and added_to_table; or error (type, message, param).
• dashboard_url string · required — The table in mySDR where these hits are, on this signal.

Credits

Free. This call never uses credits.

Errors

• 400 invalid_request — A key that is not valid, more than 100 hits, a hit without summary or with both lead and company, a source_url that is not a web address, a time that is not valid (param names it, e.g. hits[2].summary), or an unknown field.
• 404 not_found — Your organization has no signal with this key.
• 409 invalid_state — The signal is paused: do not run it, or set it active first.
• 503 service_unavailable — Own signals are not available in this environment yet.
• 409 invalid_state — The key has no user behind it, so mySDR cannot record who did it.
• 401 authentication_error — The Authorization header is missing, or the key is unknown or revoked.
• 403 permission_error — API access is not part of your plan, or your account is suspended.
• 429 rate_limit_error — More than 60 requests per minute, or more than 3 at the same time, on one key. Wait for the Retry-After header.
• 503 service_unavailable — The API is temporarily unavailable. Retry later.
• 500 internal_error — Something went wrong on our side.

Example

cURL

curl -X POST "https://mysdr.app/api/v1/agent-signals/hiring_spike/hits" \
  -H "Authorization: Bearer $MYSDR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "checked_at": "2026-10-25T07:00:00Z",
    "next_check_at": "2026-10-26",
    "note": "140 careers pages, 3 spikes",
    "hits": [
      {
        "company": {
          "name": "Acme Logistics",
          "domain": "acme-logistics.example"
        },
        "summary": "12 open roles on the careers page, up from 3 a month ago.",
        "source_url": "https://acme-logistics.example/jobs",
        "external_id": "acme-logistics.example/jobs@2026-10-25"
      }
    ]
  }'

JavaScript

const response = await fetch('https://mysdr.app/api/v1/agent-signals/hiring_spike/hits', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.MYSDR_API_KEY}`,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "checked_at": "2026-10-25T07:00:00Z",
    "next_check_at": "2026-10-26",
    "note": "140 careers pages, 3 spikes",
    "hits": [
      {
        "company": {
          "name": "Acme Logistics",
          "domain": "acme-logistics.example"
        },
        "summary": "12 open roles on the careers page, up from 3 a month ago.",
        "source_url": "https://acme-logistics.example/jobs",
        "external_id": "acme-logistics.example/jobs@2026-10-25"
      }
    ]
  })
});
const body = await response.json();

Python

import json
import os
import urllib.request

payload = {
  "checked_at": "2026-10-25T07:00:00Z",
  "next_check_at": "2026-10-26",
  "note": "140 careers pages, 3 spikes",
  "hits": [
    {
      "company": {
        "name": "Acme Logistics",
        "domain": "acme-logistics.example"
      },
      "summary": "12 open roles on the careers page, up from 3 a month ago.",
      "source_url": "https://acme-logistics.example/jobs",
      "external_id": "acme-logistics.example/jobs@2026-10-25"
    }
  ]
}

request = urllib.request.Request(
    "https://mysdr.app/api/v1/agent-signals/hiring_spike/hits",
    headers={
    "Authorization": f"Bearer {os.environ['MYSDR_API_KEY']}",
    "Content-Type": "application/json"
    },
    data=json.dumps(payload).encode(),
    method="POST",
)
with urllib.request.urlopen(request) as response:
    body = json.load(response)

Example response

{
  "object": "agent_signal_check",
  "signal": {
    "object": "agent_signal",
    "key": "hiring_spike",
    "name": "Hiring spike on careers pages",
    "description": "Companies whose careers page lists at least 10 open roles, up from fewer than 5.",
    "source": "Careers pages",
    "source_url": null,
    "schedule": "daily",
    "status": "active",
    "last_checked_at": "2026-10-25T07:00:00.000Z",
    "next_check_at": "2026-10-26T08:00:00.000Z",
    "check_overdue": false,
    "last_check_note": "140 careers pages, 3 spikes",
    "caught": {
      "leads": 0,
      "companies": 9
    },
    "last_hit_at": "2026-10-25T07:00:00.000Z",
    "via": "Grok Bot",
    "created_at": "2026-10-20T08:00:00.000Z",
    "updated_at": "2026-10-25T07:00:00.000Z",
    "results_url": "https://mysdr.app/en/gtm/companies?signal=Hiring+spike+on+careers+pages"
  },
  "recorded": 1,
  "duplicates": 0,
  "failed": 0,
  "added_to_table": 1,
  "results": [
    {
      "index": 0,
      "ok": true,
      "id": "b41e…",
      "duplicate": false,
      "row": {
        "id": "sav_2b9e8d10-7f4a-4a51-8c2e-5d1f0a3b6c77",
        "object": "company",
        "name": "Acme Logistics"
      },
      "added_to_table": true
    }
  ],
  "dashboard_url": "https://mysdr.app/en/gtm/companies?signal=Hiring+spike+on+careers+pages"
}