Skip to main content
POST
Company Enrichment API

Endpoint

This endpoint enriches a company’s profile by searching LinkedIn company data using various identifiers.

Authentication

string
required
Bearer token with your API key: Bearer YOUR_API_KEY
See the Authentication Guide for detailed setup instructions.

Request Parameters

Request Body (JSON)

At least one identifier is required:
string
LinkedIn company slug (e.g., from linkedin.com/company/openai).Example: "openai"
string
LinkedIn’s internal company ID.Example: "11130470"
string
Full LinkedIn company URL. The API will automatically extract the slug.Example: "linkedin.com/company/openai"Example: "https://www.linkedin.com/company/openai/"
string
Internal company ID from People Context API.Example: "abc123"
Identifier Priority: Identifiers are tried in this order: linkedin_slug > linkedin_id > linkedin_url (slug extracted) > company_id. The API returns as soon as a match is found.

Response

Success Response (200 OK)

Returns a JSON object containing the enriched company data.
boolean
Whether a matching company was found in the database.
object | null
Company data object (null if no match found)
string
Internal company ID
string
LinkedIn company slug
string
LinkedIn’s internal company ID
object
Company profile information
string
Company name
string
Company tagline/description
string
Full company description
string
Industry category
string
Company size range (e.g., “51-200 employees”)
integer
Approximate employee count
integer
Year founded
string
Company website URL
string
Company phone number
array
Array of company specialties/focus areas
object
Headquarters location information
string
City name
string
State/region code
string
Country name
string
Postal/ZIP code
string
Street address line 1
string
Street address line 2
object
Company media assets
Company logo URL
string
Cover/banner image URL
Additional fields may be present depending on the data available in the LinkedIn company profile.

No Match Response (200 OK)

When no matching company is found:

Error Responses

All error responses follow the standard format with a detail field:
Error Status Codes:
  • 401 Unauthorized - Missing or invalid API key
  • 403 Forbidden - Organization is inactive
  • 422 Unprocessable Entity - Validation error (missing required parameters or invalid values)
  • 429 Too Many Requests - Monthly request limit exceeded
  • 500 Internal Server Error - Unexpected server error (e.g., Elasticsearch connection failed)

Examples


Sample Response


Best Practices

URL Flexibility: You can pass full LinkedIn URLs - the API automatically extracts the company slug. This is useful when scraping or working with raw LinkedIn links.
Rate Limits: API requests are subject to rate limits based on your organization’s plan. Monitor your monthly request count to avoid hitting limits.
Data Freshness: LinkedIn company data is refreshed monthly. Check the profile data for recent updates and employee counts.

Use Cases

  • Lead Enrichment: Enrich company information from LinkedIn URLs in your CRM
  • Market Research: Build company databases with detailed profile information
  • Sales Intelligence: Get company size, industry, and location data for targeting
  • Data Validation: Verify company information against LinkedIn’s authoritative data