LinkedIn Professional Network  ·  View 09 of 30  ·  3 · Structure

Integration Catalogue

Every interface in and out, its protocol and cadence, and who owns the contract.

Editable source SVG draw.io All views
Who calls us Web client iOS / Android Partner apps ATS partners Enterprise SSO Platform LinkedIn Platform versioned APIs only What we call Delivery providers APNs · FCM · email · SMS Google / Apple URL reputation Payments Ads platform GraphQL GraphQL OAuth REST hourly feed SAML on event OIDC per link on purchase per page LinkedIn — Integration Catalogue Application we own External / third party synchronous batch event / async Kafka topics are never exposed to partners; every external contract is a versioned API. v 1.0 · owner Integration Architecture · date 2026-09

Decisions

  • Partners get OAuth 2.0 scoped tokens on versioned REST. Product clients get GraphQL, generated from the Rest.li schemas
  • Only the notification and identity services call delivery providers, each behind its own circuit breaker
  • ATS partners push job feeds in batch; feeds are validated, deduplicated and checked for fraud before they become postings

Contract ownership

  • LinkedIn owns every inbound contract. Outbound, the provider owns the contract and LinkedIn owns the adapter
  • URL reputation is checked asynchronously when a post is made, and synchronously only when a member clicks a link flagged as uncertain

Risks

  • APNs and FCM are single providers per platform with no alternative, so their outages degrade to in-app only
  • The ad call sits on the feed path. It gets a 50 ms budget and is dropped, never waited for
◀  Container Architecture All views Data Architecture and Ownership  ▶
Solution Architecture v1.0 · LinkedIn's own stack in LinkedIn-run colos · Enterprise Architecture · 2026-0909-integration-catalogue