Apex by LeadShark · Schema

GetApiV1SignalsResponse

LinkedInArtificial IntelligenceAutomationLead GenerationMCP

Properties

Name Type Description
id string Hot lead record ID
actor_name string Lead's full name
actor_linkedin_id string LinkedIn member identifier
actor_linkedin_url string LinkedIn profile URL
actor_profile_picture_url string Profile picture URL
heat_score number Composite engagement score (higher = hotter lead)
signal_count number Total number of signal events from this lead
signal_breakdown object Counts per signal type, e.g. { "comment": 5, "reaction": 3 }
top_signals array Recent signal events with type, date, and source_url
connection_status string LinkedIn relationship: FIRST_DEGREE , SECOND_DEGREE , etc.
first_seen_at string When this lead first appeared in signals
computed_at string When the heat score was last computed
View JSON Schema on GitHub

JSON Schema

apex-new-get-api-v1-signals-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/apex-new/json-schema/apex-new-get-api-v1-signals-response-schema.json",
  "title": "GetApiV1SignalsResponse",
  "x-generated": "2026-11-01",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/_ae-authored/apex-new-openapi-generated.yml#/components/schemas/GetApiV1SignalsResponse",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Hot lead record ID"
    },
    "actor_name": {
      "type": "string",
      "description": "Lead's full name"
    },
    "actor_linkedin_id": {
      "type": "string",
      "description": "LinkedIn member identifier"
    },
    "actor_linkedin_url": {
      "type": "string",
      "description": "LinkedIn profile URL"
    },
    "actor_profile_picture_url": {
      "type": "string",
      "description": "Profile picture URL"
    },
    "heat_score": {
      "type": "number",
      "description": "Composite engagement score (higher = hotter lead)"
    },
    "signal_count": {
      "type": "number",
      "description": "Total number of signal events from this lead"
    },
    "signal_breakdown": {
      "type": "object",
      "description": "Counts per signal type, e.g. { \"comment\": 5, \"reaction\": 3 }"
    },
    "top_signals": {
      "type": "array",
      "description": "Recent signal events with type, date, and source_url"
    },
    "connection_status": {
      "type": "string",
      "description": "LinkedIn relationship: FIRST_DEGREE , SECOND_DEGREE , etc."
    },
    "first_seen_at": {
      "type": "string",
      "description": "When this lead first appeared in signals"
    },
    "computed_at": {
      "type": "string",
      "description": "When the heat score was last computed"
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/apex-new-get-api-v1-signals-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.