@postqueen/node 1.0 is on npm

@postqueen/node is on npm, and 1.0.0 is the first stable release. It is a Node client for the postqueen public REST API, meant for the case where you are writing a service rather than typing commands into a terminal.

What shipped

The SDK sits on the same REST API that the web app, the CLI and the built-in MCP server all use. Authentication, channels, posts and uploads go through it, so a backend job can queue a week of content without a person opening the app at all.

The kind of thing it is for:

• A CMS publish event that fans out into scheduled posts on the channels that care about it.
• A nightly job that refills next week's queue from wherever your content calendar actually lives.
• An internal tool that shows what is scheduled, for people who do not need a full account.

The 1.0.0 number is a commitment rather than a celebration. It means the public surface is settled and follows semver from here: patches for fixes, minors for additions, a major if something has to break. Pin it if you want the version you tested to be the version that runs in six months.

How to try it

# add the SDK to a Node project
npm i @postqueen/node
 
# or pin the first stable release
npm i @postqueen/node@1.0.0

You will need an API key from your postqueen account. The SDK works against the cloud API or a self-hosted instance, since it is the same API in both places.

Source and issues are at https://github.com/GkhanKINAY/postqueen-app. If you would rather not take on another dependency, that is a reasonable call: the REST API is public and documented, and the SDK is a thin layer over it.