Skip to main content
POST
Resolve a company LinkedIn page to structured data

Authorizations

Authorization
string
header
required

Workspace API key (loice_sk_ + 48 hex characters), created under Settings → API Keys. Sent as Authorization: Bearer loice_sk_…. Invalid, missing, or expired keys are rejected with 401 before any billable work happens.

Headers

Idempotency-Key
string

Optional, 1–255 printable ASCII characters, scoped to your workspace. Send the same key when you retry the same request: the original outcome is replayed (replay: true, charged: false, pointsCharged: 0) instead of running and charging again. The same key with a different request is refused with 409 idempotency_conflict, as is a key reused after its replay record expired (kept 30 days); a key whose first request is still running answers 409 idempotency_in_progress. Without a key, every request is a new lookup, billed at most once on its own.

Required string length: 1 - 255

Body

application/json
linkedinUrl
string
required

A full LinkedIn company or school page URL (any locale subdomain, /m/, a sub-page, or a numeric id). A bare slug (microsoft) and a person, job, group or post URL are refused as invalid-input.

refresh
boolean

Bypass cached freshness and re-confirm against the source. Billed again. True only for the JSON literal true. Not available for a school (answered 422 login-required, never billed): school pages are not public, so there is no source to re-confirm against.

Response

A completed lookup — a company found, or no-such-company (charged). Inspect found, reason, charged and replay.

data
object
required