Skip to main content
All arrays in the output are sorted deterministically for consistency.

​
Person Data

​
Sorting Rules

  • Contact arrays (phones[], emails[], locations[], socials[]): current items first, then by quality
  • Experience & Education: current entries first, then by date (most recent first)
  • Skills & Languages: alphabetical

​
Contact Data Arrays

​
Phones, Emails, Locations, Socials

These arrays prioritize current, high-quality items first. You can rely on the first item being the best available contact method. Example phone array: 
"phones": [
  {"type": "mobile", "number": "+15551234567", "current": true, "confidence": "high", "num_sources": 2, "last_seen": "2026-01-15"},
  {"type": "mobile", "number": "+15559876543", "current": true, "confidence": "moderate", "num_sources": 3, "last_seen": "2025-11-20"},
  {"type": "landline", "number": "+15551111111", "current": false, "confidence": "high", "num_sources": 4, "last_seen": "2024-06-01"}
]

​
Experience & Education

These arrays place current entries first (current: true), followed by past entries sorted by date (most recent first). You can rely on experience[0] being the current or most recent job.

​
Skills & Languages

These arrays are sorted alphabetically by the cleaned value: 
"skills": [
  {"cleaned": "data analysis", "raw": ["Data Analysis"]},
  {"cleaned": "project management", "raw": ["Project Management", "PM"]},
  {"cleaned": "python", "raw": ["Python", "python3"]}
]

​
Company Data

​
Sorting Rules

  • legion_employee_count_by_month[]: reverse chronological (most recent month first)
  • domains[], socials[], tickers[]: no guaranteed ordering
Company socials[] do not include confidence, num_sources, last_seen, or current fields, so quality-based sorting does not apply. Person socials[] do include these fields and are sorted by current status and quality.

​
Headcount History

The legion_employee_count_by_month[] array places the most recent month first: 
"legion_employee_count_by_month": [
  {"month": "2026-01", "count": 8500, "net_change": 50, "growth_rate": 0.006, "hires": 120, "departures": 70},
  {"month": "2025-12", "count": 8450, "net_change": 65, "growth_rate": 0.008, "hires": 135, "departures": 70}
]

​
Why Deterministic Ordering Matters

  1. Consistency: Same data always appears in the same order
  2. Predictability: You can rely on experience[0] being the current job
  3. Filtering: Easier to find primary contact methods
  4. Testing: Deterministic output makes testing and validation easier