ApivomApivom
Get Demo

LinkedIn OAuth & Web Endpoints Connector

LinkedIn's www.linkedin.com endpoints used by Talent Solutions partners — obtain customer and child-application access tokens for Recruiter System Connect, Talent CRM Connect and Apply with LinkedIn, and fetch an applicant's résumé and cover letter for Apply Connect — registered in Apivom Atlas for ATS and recruiting-tech tenants.

What you can do

  • Customer application access tokens for Recruiter System Connect and Talent CRM Connect (current and versioned forms)
  • Child-application tokens for Apply with LinkedIn v3, Recruiter System Connect and Talent CRM Connect
  • Apply Connect: download the applicant's résumé and cover letter files for a job application
  • Eight routes on www.linkedin.com (one read-only), documented in the AI integration guide (llms.txt)

Use cases

  • Provision Recruiter System Connect per customer — Exchange your partner credentials for each customer's application token as they enable the integration, and keep the tokens encrypted per tenant.
  • Pull the application files — Fetch the résumé and cover letter of an Apply Connect candidate into your ATS record the moment the application arrives.

Most of LinkedIn's APIs live on api.linkedin.com, but a handful of partner endpoints sit on www.linkedin.com itself, and this connector collects them. They belong to the Talent Solutions partner programs: Recruiter System Connect and Talent CRM Connect let an applicant-tracking or candidate-relationship system integrate with LinkedIn Recruiter, and each customer that enables the integration needs a customer application access token — obtained here, in the current and the versioned form — or a child-application token when the partner provisions per-customer apps. Apply with LinkedIn v3 uses the same child-application token route. The one read-only route is Apply Connect's résumé-and-cover-letter download, which returns the files a candidate attached when applying through LinkedIn. Apivom Atlas registers all eight routes with per-tenant logging and the AI integration guide (llms.txt). No Apivom product workflow uses these endpoints today — they are available to tenants building ATS or recruiting integrations under LinkedIn's partner programs, and a product workflow is scoped per customer. Note that the general OAuth 2.0 authorization-code flow for members and company pages is not in this catalogue.

Authentication

No stored credential: these routes exchange your LinkedIn partner application's client id and secret (and, for child applications, the customer's grant) for access tokens that the other LinkedIn connectors then send as Bearer. Apivom Atlas forwards the exchange and stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Is this the LinkedIn sign-in / company-page OAuth flow?

No. These are the Talent Solutions partner token endpoints (Recruiter System Connect, Talent CRM Connect, Apply with LinkedIn) plus the Apply Connect file download. The member authorization-code flow used to connect a company page is a separate LinkedIn flow outside this catalogue.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.