Loading…
Interactive documentation for this atlas's own API. These are first-party endpoints over stored research data — they are not LinkedIn APIs and never proxy LinkedIn traffic.
Generated from the live OpenAPI 3 specification at /openapi.json.
Loading OpenAPI specification…
ATLAS_BASE="https://<your-atlas-host>"
curl -sS "$ATLAS_BASE/api/ready"
curl -sS "$ATLAS_BASE/api/v1/summary"
curl -sS "$ATLAS_BASE/api/v1/endpoints?feature=authentication&confidence=confirmed"
curl -sS "$ATLAS_BASE/api/v1/diff?from=1.0&to=3.0.1"
curl -sS "$ATLAS_BASE/openapi.json"{
"id": "ep_d5528bb3725ac6e3",
"service": "linkedin",
"observed_in_versions": ["1.0", "1.0.1", "1.0.4", "1.5", "3.0.1"],
"historical_host": "m.linkedin.com",
"historical_path_template": "/oauth/request_token",
"http_method": "POST",
"request_model": "TTOAuthRequestModel",
"authentication_type": "oauth1_consumer_only",
"static_confidence": "confirmed",
"live_status": "retired_or_gone",
"http_status": 301
}Reference only. These are recovered evidence records, not executable production calls.
| Method | Historical path | Host | Confidence | Detail |
|---|---|---|---|---|
| GET | /v2/messages | m.linkedin.com | confirmed | evidence → |
| GET | /v2/messages/count.xml | m.linkedin.com | confirmed | evidence → |
| POST | /oauth/login_authorize | m.linkedin.com | confirmed | evidence → |
| POST | /v2/members/{memberId}/invite | m.linkedin.com | candidate | evidence → |
| GET | /v2/members/{memberId}/connections?fields=... | m.linkedin.com | strong | evidence → |
| POST | /v2/messages/{messageId}/reply | m.linkedin.com | strong | evidence → |
| GET | /profile | m.linkedin.com | strong | evidence → |
| GET | /contacts | m.linkedin.com | candidate | evidence → |
| GET | /v2/messages/{messageId} | m.linkedin.com | strong | evidence → |
| GET | /v2/pymk | m.linkedin.com | candidate | evidence → |
| GET | /members/{memberId}/connections | m.linkedin.com | strong | evidence → |
| GET | /search | m.linkedin.com | candidate | evidence → |
| POST | /v2/network_updates/{updateId}/comments | m.linkedin.com | strong | evidence → |
| POST | /v2/favorites/{favoriteId}/destroy | m.linkedin.com | candidate | evidence → |
| POST | /v2/favorites | m.linkedin.com | candidate | evidence → |
| POST | /oauth/request_token | m.linkedin.com | confirmed | evidence → |
| GET | /v2/invitations | m.linkedin.com | strong | evidence → |
| GET | /v2/network_updates | m.linkedin.com | strong | evidence → |
| POST | /v2/messages/{messageId}/archive | m.linkedin.com | strong | evidence → |
A 200 with an HTML login page is not verified data. See the precise definition of each status on the methodology page and at /api/v1/status-definitions.