Skip to main content
Lightweight profile: name, avatar, location, followers, public id, current company, and a basic experience/education list (company + dates; job titles, the current-role flag and the connections label only where the source and the profile show them; no descriptions or skills; past companies may be redacted). For full experience detail, skills, certifications, and verified flags use linkedin.profile. This page is the seller-facing summary of one catalog API, linkedin.profile_thin. The transport rules that apply to every API a seller serves - signed requests, the response envelope, timeouts, and body limits - are on the operator endpoint contract.

The price you compete with

AnyAPI publishes this API from $0.80 per 1,000 requests. That is the price a buyer sees today, so it is the price your endpoint has to come in under to win traffic.

The request your endpoint receives

The response your endpoint must return

Extra fields are kept, missing declared fields fail.

Fields that must never come back empty

  • experience
The repository marks these fields as ones every source must be able to fill. An empty value is only correct when the entity itself genuinely has nothing there.

Not found, and how it differs from empty

When the entity does not exist, answer 2xx with the not-found shape:
An empty list is not a not-found: when the entity exists and has nothing to return, answer 2xx with found: true and an empty articles array. This output schema declares no reason field, so found: false is the whole not-found answer.

Example request

The registration tests send this example to your endpoint, with the API’s other test inputs. After that, the real-request check sends your endpoint real past customer inputs, and an AI reviewer compares each answer with AnyAPI’s own answer to the same input.

Next