Using Signals API
Using the Signals API
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
Filter signals by company domain (e.g., "acme.com")
acme.comPattern: ^[a-zA-Z0-9]([a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?(\.[a-zA-Z0-9]([a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?)*$Filter signals by company ID
comp_abc123Maximum number of results per page
25Example: 25Number of results to skip for pagination
0Example: 0Filter signals completed on or after this date (RFC3339 format)
2024-01-01T00:00:00ZFilter signals completed on or before this date (RFC3339 format)
2024-12-31T23:59:59ZFilter signals by subscription ID (UUID of the signal subscription that triggered execution)
a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6dSignals retrieved successfully
Total number of signals matching the filters
42Maximum results per page
25Number of results skipped
0Number of results in this response
25Bad Request - Invalid parameters
Unauthorized - Invalid or missing API key
Internal Server Error
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
The UUID of the signal subscription
a12b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6dFilter signals by company domain
acme.comFilter signals by company ID
b23c4d5e-6f7a-8b9c-0d1e-2f3a4b5c6d7eMaximum number of results per page
25Example: 25Number of results to skip for pagination
0Example: 0Filter signals completed on or after this date (RFC3339 format)
2024-01-01T00:00:00ZFilter signals completed on or before this date (RFC3339 format)
2024-12-31T23:59:59ZSubscription logs retrieved successfully
Total number of signals matching the filters
42Maximum results per page
25Number of results skipped
0Number of results in this response
25Bad Request - Invalid subscription ID format
Unauthorized - Invalid or missing API key
Not Found - Subscription does not exist or does not belong to this organization
Internal Server Error
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
The unique identifier of the signal (UUID format)
e45c1dc4-d422-4b51-956b-cb6d3ddaf250Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$Signal retrieved successfully
Polymorphic signal response (company or contact)
Unauthorized - Invalid or missing API key
Signal not found or access denied
Internal Server Error
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
The external identifier of the contact research request (e.g., HubSpot contact ID)
hubspot_12345The source system that provided the external ID (e.g., "hubspot")
hubspotContact research retrieved successfully
Unique identifier for the contact research request
cr_abc123def456Current processing status of the contact research
completedPossible values: First name of the contact
JohnLast name of the contact
DoeCompany name
Acme CorpCompany domain
acme.comTimestamp when the research request was created
2024-01-15T10:30:00ZContact profile URL if provided (e.g., LinkedIn or other professional profile)
https://linkedin.com/in/johndoeJob title - prioritizes the title found during research (profile.currentRole), falls back to the title provided in the request if research didn't find one
VP of SalesProfessional interests and topics (only present when status is "completed")
Potential challenges or pain points (only present when status is "completed")
Error message if status is "failed"
Could not retrieve LinkedIn profile dataTimestamp when the research completed (success or failure)
2024-01-15T10:35:00ZBad Request - Malformed request body
Unauthorized - Invalid or missing API key
Not Found - Contact research not found or access denied
Unprocessable Entity - Validation error
Internal Server Error
Start a contact research job — AI gathers insights from LinkedIn and other sources asynchronously; use contacts.get_research to poll for results
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
First name of the contact
JohnLast name of the contact
DoeName of the contact's company
Acme CorpCompany domain (e.g., "acme.com")
acme.comPattern: ^[a-zA-Z0-9]([a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?(\.[a-zA-Z0-9]([a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?)*$Contact profile URL of the contact (e.g., LinkedIn or other professional profile, optional)
https://linkedin.com/in/johndoeLinkedIn Sales Navigator profile URL of the contact (optional)
https://www.linkedin.com/sales/lead/ACwAAABcD...Job title of the contact (optional)
VP of SalesOptional webhook URL to receive notifications when processing completes
https://myapp.com/webhooks/contact-researchContact research request created successfully
Bad Request - Malformed request body (invalid JSON)
Unauthorized - Invalid or missing API key
Unprocessable Entity - Validation error
Too Many Requests - Rate limit exceeded
Internal Server Error
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
The unique identifier of the contact research request
cr_abc123def456Contact research retrieved successfully
Unique identifier for the contact research request
cr_abc123def456Current processing status of the contact research
completedPossible values: First name of the contact
JohnLast name of the contact
DoeCompany name
Acme CorpCompany domain
acme.comTimestamp when the research request was created
2024-01-15T10:30:00ZContact profile URL if provided (e.g., LinkedIn or other professional profile)
https://linkedin.com/in/johndoeJob title - prioritizes the title found during research (profile.currentRole), falls back to the title provided in the request if research didn't find one
VP of SalesProfessional interests and topics (only present when status is "completed")
Potential challenges or pain points (only present when status is "completed")
Error message if status is "failed"
Could not retrieve LinkedIn profile dataTimestamp when the research completed (success or failure)
2024-01-15T10:35:00ZNot Found - Contact research not found or access denied
Internal Server Error
Search for contacts at a company via LinkedIn Sales Navigator — requires a LinkedIn Sales Navigator connection on the API key owner's account
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
LinkedIn company URLs to scope the search. Supports multiple companies. Omit to search across all companies.
["https://linkedin.com/company/google"]First name of the contact to search for
JohnLast name of the contact to search for
DoeJob titles to search for
["Engineering Manager","VP Engineering"]Keywords to search for in contact profiles (e.g., skills, technologies)
Kubernetes, DevOpsCountries to filter contacts by location (ISO 3166-1 alpha-2 codes)
["US","GB","DE"]Contact search completed successfully
Total number of contacts found
15Whether LinkedIn Sales Navigator is connected for the user
trueBad Request - Invalid input
Unauthorized - Invalid or missing API key
Unprocessable Entity - Could not process LinkedIn URL
Too Many Requests - Rate limit exceeded
Internal Server Error
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
Filter signals by contact profile URL (LinkedIn or other professional profile)
https://linkedin.com/in/johndoeMaximum number of results per page
25Example: 25Number of results to skip for pagination
0Example: 0Contact signals retrieved successfully
Bad Request - Invalid parameters
Unauthorized - Invalid or missing API key
Internal Server Error
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
The unique identifier of the contact signal (UUID format)
e45c1dc4-d422-4b51-956b-cb6d3ddaf250Pattern: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$Contact signal retrieved successfully
Polymorphic signal response (company or contact)
When the signal processing completed (only present when status is completed)
2024-01-15T10:32:15ZThe AI-generated answer (only present when status is completed)
Detailed reasoning for the answer (only present when status is completed)
Based on the company's website and public information, Acme Corp specializes in enterprise software.Confidence score for the answer (0-1, only present when status is completed)
0.95Error message (only present when status is failed)
LinkedIn data is currently unavailable due to rate limits. Please try again later.Machine-readable error code (only present when status is failed)
LINKEDIN_RATE_LIMIT_EXCEEDEDPossible values: Suggested action to resolve the error (only present when status is failed)
You can: (1) Set connectors.salesNavigator.enabled="off" to skip LinkedIn data, (2) Add more LinkedIn connectors, or (3) Try again in 24 hours when rate limits reset.Verification mode used for signal generation
strictPossible values: Contact profile URL (LinkedIn or other professional profile)
https://linkedin.com/in/johndoeUnauthorized - Invalid or missing API key
Signal not found or access denied
Internal Server Error
Get remaining credits balance — returns how many API credits your organization has left in the current billing period
API key authentication using Bearer token. Format: sk_live_ followed by a secure random string.
Credit balance retrieved successfully
Remaining credits balance for the organization in the current billing period
Number of credits remaining in the current billing period. Each signal creation consumes one credit. Returns 0 when the organization has no credits left; credits reset at the start of each new billing period.
58Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
Internal Server Error
Last updated