Give it a LinkedIn profile URL — get structured JSON back.
Name · headline · about · location · experience · education · skills · certifications · languages · images
sahil-patani-2721231b8 is pre-loaded on the server, so it needs no login.
curl "{origin}/api/v1/profile?url=sahil-patani-2721231b8"
This service stores no LinkedIn credentials — deliberately. A public endpoint backed by one person's account would put that account at unbounded risk. So you bring your own session, used for your request only and never stored or logged.
li_at is about 150 characters. The DevTools table truncates it
— copy from the detail box below the grid, not the cell.
No API key. The endpoint is intentionally open; what bounds abuse is a per-session rate limit, not a shared secret.
Deliberately slow. One profile per ~45 seconds, 50 a day, counted per LinkedIn session rather than globally. That pacing is what keeps accounts safe.
Every response says where it came from. meta.source
is voyager-dash when fetched live, or cache-* when
it was already held.