​

LinkedIn Company Documentation

Technical field definitions for LinkedIn company endpoint.

​

Overview

Extracts structured company data from LinkedIn company pages. Returns JSON with organizational information, industry classification, size metrics, and locations.

​

Response Fields

​

Basic Information

id (integer)

• Unique identifier assigned by WraithBytes
• Auto-incremented database primary key
• Use for tracking and referencing scrape records

url (string)

• LinkedIn company page URL that was scraped
• Format: https://www.linkedin.com/company/{company-slug}
• Normalized to canonical form

name (string)

• Official company name as displayed on LinkedIn
• May include legal suffixes (Inc., LLC, Ltd., etc.)
• UTF-8 encoded, supports international characters

​

Classification

industry (string)

• Primary industry category
• LinkedIn’s predefined taxonomy
• Examples: “Information Technology and Services”, “Financial Services”, “Computer Software”
• Single value (not multi-industry)

type (string)

• Organizational structure type
• Possible values:
  • “Public Company”
  • “Privately Held”
  • “Non-profit”
  • “Partnership”
  • “Educational Institution”
  • “Government Agency”
  • “Self-Employed”
  • Others (LinkedIn taxonomy)

​

Size & Scale

company_size (string)

• Employee count range
• Format: ”- employees”
• Standard ranges:
  • “1-10 employees”
  • “11-50 employees”
  • “51-200 employees”
  • “201-500 employees”
  • “501-1000 employees”
  • “1001-5000 employees”
  • “5001-10000 employees”
  • “10001+ employees”
• Self-reported by company admin, may be outdated

employee_count (integer)

• Approximate employee count
• Calculated by LinkedIn based on member profiles listing this company
• More dynamic than company_size
• May undercount if employees don’t list company on LinkedIn

​

Location

headquarters (string)

• Primary office location
• Format: “City, State/Region” or “City, Country”
• Examples: “San Francisco, CA”, “London, UK”

locations (array of strings)

• Additional office locations
• May include headquarters
• Format same as headquarters field
• Unordered

​

Temporal

founded (string)

• Year company was founded
• Format: “YYYY”
• May be null if not provided

​

Business Details

specialties (array of strings)

• Company focus areas and expertise
• User-defined keywords
• Unordered
• Examples: [“Cloud Computing”, “Artificial Intelligence”, “SaaS”]

about (string)

• Company description
• Free-form text, length varies (typically 500-2000 characters)
• Contains company mission, products, services
• May include recent achievements or news

​

Contact & Web Presence

website (string)

• Primary company website URL
• Format: Full URL including protocol
• Example: “https://www.example.com”

phone (string)

• Main company phone number
• Format varies by country
• May be null if not provided

linkedin_url (string)

• LinkedIn company page URL
• Same as url field

twitter_url (string)

• Company Twitter/X profile URL
• May be null

facebook_url (string)

• Company Facebook page URL
• May be null

​

Metadata

scraped_at (string)

• Timestamp of scrape
• Format: ISO 8601 (e.g., “2025-01-10T12:00:00Z”)
• UTC timezone

created_at (string)

• Record creation timestamp in WraithBytes database
• Format: ISO 8601
• UTC timezone

​

Data Notes

​

Company Size vs Employee Count

• company_size: Static range set by admin, may be outdated
• employee_count: Dynamic count from LinkedIn member data, more current
• Discrepancies are common; employee_count is generally more accurate for recent data

​

Field Completeness

• Always present: id, url, name, scraped_at, created_at
• Usually present: industry, company_size, headquarters
• Often present: about, website, employee_count
• Sometimes present: specialties, locations, founded
• Rarely present: phone, twitter_url, facebook_url

​

Data Accuracy

• Self-reported by company administrators
• Not verified by LinkedIn or WraithBytes
• Update frequency varies by company engagement
• Social media links may be outdated

​

Technical Specifications

• Response Format: JSON
• Encoding: UTF-8
• Date Formats: ISO 8601 for timestamps, “YYYY” for founded year
• Max Response Size: Varies (typically 5-20KB per company)
• Null Values: Most fields can be null if not provided by company

View API Reference →