Post Publisher
LinkedIn Publishing CLI

Ship posts from the terminal without babysitting a browser tab.

Post Publisher is a command-line workflow for authenticating with LinkedIn and publishing text, image, and document posts with one consistent interface. Bring your own LinkedIn app credentials, sign in once, and make your posting flow scriptable and repeatable.

Install

Get the CLI in one line

Windows (PowerShell):

irm https://post-publisher.ccisne.dev/install.ps1 | iex

Linux (bash):

curl -fsSL https://post-publisher.ccisne.dev/install.sh | bash

The installer downloads the latest release binary from GitHub and adds it to your PATH. You can read both scripts before running them: install.ps1 · install.sh.

Quick start

Authenticate and publish

Post Publisher does not ship shared secrets. You create your own LinkedIn Developer app (enable Sign in with LinkedIn using OpenID Connect and Share on LinkedIn), then point the CLI at it:

post-publisher auth configure
post-publisher auth login
post-publisher post text --message "Hello, LinkedIn!"

Publish images and PDFs the same way with post image and post document. The command is post-publisher, with pp as a short alias. After signing in once, posting is fully scriptable until the token expires (~60 days), then you sign in again.

What this site is for

Public product identity for the LinkedIn app

This site is the public home of the Post Publisher LinkedIn Developer App: a clear product page, a reachable privacy policy, and a contact route. Its job is trust, documentation, and compliance — not marketing.

CLI package

The technical package name is post_publisher. The public app name is Post Publisher.

Auth model

Uses 3-legged OAuth with OpenID Connect, profile, email, and member social posting scopes.

Formats

Publish text, images, and PDF documents — all validated end to end against the live LinkedIn API.

How it works

From install to published post

  1. Install the CLI with the one-line command above.
  2. Configure it with your own LinkedIn app's client ID, secret, and redirect URI.
  3. Sign in once through the browser; the token is cached locally.
  4. Publish text, image, or document posts — manually or from a script.