The API that also writes the content

Client credentials, no user session

Every app you create has its own client identifier and secret. You request a token through the client credentials flow against our own endpoint (the same domain as the rest of the API) and start calling: no cookies, no user in the middle and no renewing OAuth network by network.

curl -X POST "https://api.planvortex.com/v1.0.0/oauth/token" \
  -d grant_type=client_credentials \
  -d client_id=$APP_CLIENT_ID \
  -d client_secret=$APP_SECRET

Tokens expire. Careful: expiry does NOT arrive as a 401, it arrives as a 400 with code 501 or 522 in the body. Request a new one with the same call.

With the Node library you never write this call: it makes it for you, caches the token and renews it before it expires.

Publish in a handful of lines

Pick the account and the target network, send the text and any files you uploaded beforehand, and PlanVortex takes care of the rest. Add a publish date and it gets scheduled instead of going out right away. From Node, the official library brings the types and handles the token, the retries and the multipart.

import { PlanVortex } from "planvortex";

const pv = new PlanVortex({ clientId, clientSecret });

const upload = await pv.uploads.create(org, { file: "./hogaza.jpg" });
const post = await pv.publications.create(org, account, {
    social_network: "instagram",
    text: "Nuevo horno, nuevas hogazas",
    files: [upload._id],
    publish_date: new Date("2026-09-01T10:00:00Z"),
});