Slices

Social publishing

Post to Instagram, Threads, X and LinkedIn from your app, on Chirio.

The publish slice lets your app post to Instagram, Threads, X, LinkedIn and Supa Hub through Chirio: one call, up to ten accounts, now or at a set time. It is an add-on by Dopler. No surface requires it, so it is asked for by name:

Bash

node scripts/scaffold.mjs --surfaces landing,dashboard --slices publish --out ../my-app

It adds no dependency and no screen. src/lib/publish/chirio.ts is a server-only library; what to post, and who may post it, is your app's call.

Connect an account

import { connectAccountUrl } from "@/lib/publish/chirio";

const authUrl = await connectAccountUrl({
  platform: "threads",
  profileId: user.id,
  redirectUrl: "https://your-app.com/settings/social",
});
// Send the user to authUrl. They come back with ?status=success&accountId=...

Store the accountId: it stays the same if the user reconnects. listAccounts(profileId) lists what is connected.

Publish

"use server";
import { publishPost } from "@/lib/publish/chirio";

const { post } = await publishPost({
  content: "We just shipped dark mode.",
  platforms: [{ platform: "threads", accountId }],
  idempotencyKey: `release-${version}`,
});
const failed = post.targets.filter((t) => t.status === "failed");

A post goes live publicly as soon as publishPost() returns, so publish only what the user confirmed. Each network settles on its own: read post.targets[].status, not the HTTP status. Add publishAt (ISO 8601) to schedule instead.

Setup

Sign in at chirio.dev and create an API key under Settings → API keys.
Set CHIRIO_API_KEY. The same key serves the feedback and screenshots slices.

Without the key every call throws ChirioError with code not_configured.

Cost

Each target that publishes is one network write on your Chirio plan. The Free plan stops at its allowance: the call throws quota_exceeded with a message naming what is left, and nothing is published. Paid plans bill the excess as overage. Full API: docs.chirio.dev.

Last updated November 1, 2026

Edit this page on GitHub