Skip to main content

LinkedIn Company Scraping API Reference

Extract comprehensive data from LinkedIn company pages including company information, employee data, industry details, and organizational insights. Our company scraping service provides structured data for market research, sales intelligence, and competitive analysis.

Scrape LinkedIn Company

curl -X POST "https://api.mdb.tools/v1/linkedin/company" \
  -H "x-api-key: your-api-key-here" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "example-corp",
    "cached": true
  }'

Request Body

id
string
required
The LinkedIn identifier for the company to scrape. Accepts multiple formats:
  • LinkedIn Company ID: "example-corp"
  • LinkedIn Company URL: "https://linkedin.com/company/example-corp"
  • LinkedIn URN: "li:company:123456789"
cached
boolean
default:"true"
Whether to return cached data or fetch fresh data:
  • true (default): Return data up to 30 days old for faster response
  • false: Fetch fresh data no more than 1 minute old

Response

{
  "result": {
    "name": "Midbound",
    "overview": "Outbound tactics have become intrusive noise, while inbound strategies often leave us passively waiting for engagement. It's time to bridge the gap and connect with buyers where they are. \n\nMidbound identifies anonymous website visitors at the person and company level, enabling marketing and sales teams to uncover the dark funnel, optimize ad spend, and discover untapped markets.\n\nGet started for free at midbound.ai",
    "linkedin_id": "midbound",
    "picture_url": "https://cdn.mdb.tools/midbound.jpg",
    "website_url": "https://www.midbound.ai/",
    "industry": "Marketing and Advertising",
    "type": "Privately Held",
    "address_street": "123 Main Street",
    "address_city": "Dover",
    "address_state": "Delaware",
    "address_postal_code": "19901",
    "address_country": "United States",
    "address_country_code": "US",
    "revenue_range": "5M-10M",
    "employee_count": 3,
    "deleted": false
  },
  "processing_time_ms": 1850,
  "request_id": "01ARZ3NDEKTSV4RRFFQ69G5FAV"
}

Response Fields

Result Object

result
object
Contains the complete LinkedIn company data and information.
result.name
string
Official company name as displayed on LinkedIn.
result.overview
string
Company description or about section content from LinkedIn.
result.linkedin_id
string
LinkedIn company identifier/username extracted from the company URL.
result.picture_url
string
URL to the company’s profile picture or logo.
result.website_url
string
Company’s official website URL.
result.industry
string
Industry category the company operates in.
result.type
string
Company type (e.g., “Privately Held”, “Public Company”, “Non-profit”).
result.address_street
string
Street address of the company’s main office.
result.address_city
string
City where the company is headquartered.
result.address_state
string
State, region, or province of the company’s headquarters.
result.address_postal_code
string
Postal or ZIP code of the company’s address.
result.address_country
string
Country where the company is headquartered.
result.address_country_code
string
Two-letter country code for the company’s location.
result.revenue_range
string
Estimated revenue range (e.g., “5M-10M”, “100M-500M”). This field may not be available for all companies.
result.employee_count
number
Number of employees at the company.
result.deleted
boolean
Indicates whether the company page has been deleted or is no longer accessible.

Caching Information

cached
boolean
Indicates whether the response was served from cache. Only present when cached data is returned.
cache_age_hours
number
Age of the cached data in hours. Only present when cached data is returned.

Metadata Fields

processing_time_ms
number
Time taken to process the request in milliseconds.
request_id
string
Unique identifier for this request (ULID format).

Supported Identifier Formats

LinkedIn Company ID

The simplest format, typically found in LinkedIn company URLs:
{
  "id": "example-corp"
}

LinkedIn Company URL

Full LinkedIn company page URL:
{
  "id": "https://linkedin.com/company/example-corp"
}

LinkedIn URN (Uniform Resource Name)

LinkedIn’s internal identifier format:
{
  "id": "li:company:123456789"
}

Caching Behavior

Cached Requests (cached: true)

  • Data freshness: Up to 30 days old
  • Response time: Faster (typically 100-300ms)
  • Use case: Most market research and business intelligence scenarios
  • Cost: Custom pricing

Fresh Requests (cached: false)

  • Data freshness: No more than 1 minute old
  • Response time: Slower (typically 2-8 seconds)
  • Use case: When you need the most current company information
  • Cost: Custom pricing for real-time scraping
We recommend using cached requests for most use cases. Company information typically doesn’t change frequently, making cached data suitable for most business purposes while providing much faster response times.

Error Responses

When the request fails due to validation or other errors, you’ll receive a standard error response instead of the result structure. For detailed error information, see Common Error Codes.

Invalid LinkedIn Company ID

{
  "error": "validation_error",
  "message": "LinkedIn company identifier format is invalid",
  "code": "LINKEDIN_003",
  "request_id": "01ARZ3NDEKTSV4RRFFQ69G5FB8",
  "details": {
    "id": "invalid-company-id",
    "supported_formats": ["LinkedIn Company ID", "LinkedIn Company URL", "LinkedIn URN"]
  }
}

Company Not Found

{
  "error": "not_found",
  "message": "LinkedIn company not found or not accessible",
  "code": "LINKEDIN_004",
  "request_id": "01ARZ3NDEKTSV4RRFFQ69G5FB9",
  "details": {
    "id": "nonexistent-company-123"
  }
}

Missing ID Parameter

{
  "error": "bad_request",
  "message": "Missing required parameter",
  "code": "REQ_002",
  "request_id": "01ARZ3NDEKTSV4RRFFQ69G5FBA",
  "details": {
    "missing_parameter": "id",
    "parameter_type": "string"
  }
}
Note: Error responses follow the standard error format and do not include the result object. Only successful responses contain the result structure with company data.

Rate Limits

This endpoint is subject to rate limits. See Rate Limits for detailed information about usage limits and caching best practices.