Devenia Learn / Dictionary

How to set up the LinkedIn API for WordPress

A LinkedIn API integration connects a WordPress site or workflow to approved LinkedIn capabilities for publishing, identity, or data exchange.

Ask about How to set up the LinkedIn API for WordPress

Start with email. Share the page or your question, and we will answer clearly.

Art Deco service diagnosis machine with gauges, a magnifying lens, connected pipes, a speed dial, a repair wrench, and a teal signal light

Choose the LinkedIn action first

Decide whether WordPress should publish to a member profile, publish to a company Page or offer LinkedIn sign-in. These are different capabilities. Check that your chosen WordPress integration supports the action before creating an app.

For example, a consultant sharing new articles needs publishing access. A successful LinkedIn sign-in alone does not establish that the integration can publish those articles.

Does the integration require your own app?

Open its LinkedIn connection settings and follow the route it provides.

It offers a hosted connection

If the integration provides a managed connection, follow its Connect instructions. Check the app name, requested access and destination account before approving. Do not create a separate app unless the integration asks you to.

It asks for a Client ID and Client Secret

Use the app setup below. First locate the integration’s callback URL and its list of required LinkedIn products or permissions. Those details are specific to the integration; a callback copied from another plugin’s guide may be wrong.

Set up an app-based connection

Use these steps when your WordPress integration requires your own LinkedIn app.

1. Create the app and enable the product

In the LinkedIn Developer Portal, create or select the app and complete the requested details. Under Products, request the capability your integration needs. For member publishing, Share on LinkedIn provides w_member_social. Do not assume this also grants company Page publishing.

2. Register the callback and save the app details

In Auth, register the HTTPS callback supplied by your integration. Enter the app’s Client ID and Client Secret in the integration’s protected settings. Keep the secret out of public pages and support messages. LinkedIn documents this authorisation flow.

3. Connect and check the destination

Start Connect from WordPress, sign in on LinkedIn and review the requested access. After returning to WordPress, check the connected identity and publishing destination. Preview a prepared post; before any test publication, confirm the text, link, image and intended audience.

If the connection does not complete

Use the exact error message to identify the next check.

Redirect or callback error

Compare the callback requested by the integration with the registered Redirect URL in the app’s Auth settings. Check the HTTPS scheme, host and path. If WordPress has moved to another domain, obtain the current callback from its connection settings.

Missing access or failed publishing

Check the app’s available scopes and product approval status. Confirm that the integration supports the selected destination. Changed permissions require renewed member consent; an expired or revoked connection may also need reconnection. Signing in successfully does not prove publishing access.

Get help with the step that failed

Send the WordPress integration’s name, whether you are connecting a member profile or company Page, and the exact error. Include which step failed. Remove secrets and tokens from any screenshot.

Ask about the connection
Art Deco service diagnosis machine with gauges, a magnifying lens, connected pipes, a speed dial, a repair wrench, and a teal signal light