Apex by LeadShark · Schema
GetApiLeadsResponse
LinkedInArtificial IntelligenceAutomationLead GenerationMCP
Properties
| Name | Type | Description |
|---|---|---|
| id | string | Lead record ID (UUID) |
| name | string | Full name |
| title | string | LinkedIn headline / job title |
| linkedin_url | string | LinkedIn profile URL |
| source | string | Automation or source name |
| created_at | string | When the lead was captured (ISO 8601) |
| updated_at | string | Last update time (ISO 8601) |
| commenter_id | string | LinkedIn member URN |
| post_id | string | LinkedIn post ID if from a post |
| linkedin_username | string | LinkedIn username |
| first_name | string | First name (when available) |
| icp_headline_fit | string | ICP Fit label: fit | maybe | not |
| icp_headline_pct | number | ICP Fit match, 0–100 |
| icp_headline_confidence | number | How readable the headline was, 0–100 |
| icp_headline_at | string | ISO timestamp of the headline read |
| icp_score | number | Compatibility mirror of icp_headline_pct / 100 |
| lead_type | string | automation | post_engagement | connection_requests |
| engagements | array | Engagement events (e.g. comments) |
| icp_fit | string | Quiz outcome: fit | maybe | not |
| archived | boolean | Whether the lead is archived |
| enriched_profile | object | Full profile JSON from on-demand enrichment |
| enriched_at | string | When the lead was last enriched (ISO 8601) |
| string | Work email (if enriched) |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/apex-new/json-schema/apex-new-get-api-leads-response-schema.json",
"title": "GetApiLeadsResponse",
"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/GetApiLeadsResponse",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Lead record ID (UUID)"
},
"name": {
"type": "string",
"description": "Full name"
},
"title": {
"type": "string",
"description": "LinkedIn headline / job title"
},
"linkedin_url": {
"type": "string",
"description": "LinkedIn profile URL"
},
"source": {
"type": "string",
"description": "Automation or source name"
},
"created_at": {
"type": "string",
"description": "When the lead was captured (ISO 8601)"
},
"updated_at": {
"type": "string",
"description": "Last update time (ISO 8601)"
},
"commenter_id": {
"type": "string",
"description": "LinkedIn member URN"
},
"post_id": {
"type": "string",
"description": "LinkedIn post ID if from a post"
},
"linkedin_username": {
"type": "string",
"description": "LinkedIn username"
},
"first_name": {
"type": "string",
"description": "First name (when available)"
},
"icp_headline_fit": {
"type": "string",
"description": "ICP Fit label: fit | maybe | not"
},
"icp_headline_pct": {
"type": "number",
"description": "ICP Fit match, 0–100"
},
"icp_headline_confidence": {
"type": "number",
"description": "How readable the headline was, 0–100"
},
"icp_headline_at": {
"type": "string",
"description": "ISO timestamp of the headline read"
},
"icp_score": {
"type": "number",
"description": "Compatibility mirror of icp_headline_pct / 100"
},
"lead_type": {
"type": "string",
"description": "automation | post_engagement | connection_requests"
},
"engagements": {
"type": "array",
"description": "Engagement events (e.g. comments)"
},
"icp_fit": {
"type": "string",
"description": "Quiz outcome: fit | maybe | not"
},
"archived": {
"type": "boolean",
"description": "Whether the lead is archived"
},
"enriched_profile": {
"type": "object",
"description": "Full profile JSON from on-demand enrichment"
},
"enriched_at": {
"type": "string",
"description": "When the lead was last enriched (ISO 8601)"
},
"email": {
"type": "string",
"description": "Work email (if enriched)"
}
}
}
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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/apex-new-get-api-leads-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.