# How to Post to Social Media with Node.js (2026) · PostLake

> Markdown version of https://postlake.dev/guides/nodejs . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

Post to social media with *Node.js*.

PostLake's publish API is ordinary JSON over HTTPS. Node 18+ needs no SDK. Match the docs: address a profile, then read each target in the response.

**In short:** In Node 18+. One fetch to /v1/posts publishes across the profile. Check targets[]; use Idempotency-Key on retries.

## When this guide is for you

Your service already runs on Node and you want outbound social posts without nine OAuth integrations.

## Before you start

Same setup the [docs quickstart](https://docs.postlake.dev/quickstart.md) uses. Do this once:

- Sign up at [app.postlake.dev](https://app.postlake.dev) and verify your email (unlocks free credits).
- On **Channels**, create a **profile** (e.g. `my-brand`) and connect at least one account. **Bluesky is the fastest first channel**: no app review. Instagram/TikTok/Facebook need each platform's review before API posting.
- Account menu → **API Keys** → create a key (`sk_live_…`). It shows once; treat it like a password.


## Working example in Node.js

Connect accounts once in the dashboard, then this is the publish call:

```
const resp = await fetch("https://api.postlake.dev/v1/posts", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.POSTLAKE_API_KEY}`,
    "Content-Type": "application/json",
    "Idempotency-Key": "hello-node-001",
  },
  body: JSON.stringify({
    text: "Hello from Node 👋",
    profile: "my-brand",
    // platforms: ["bluesky", "linkedin"], // optional filter
  }),
});

const post = await resp.json();
if (!resp.ok) throw new Error(JSON.stringify(post));
console.log(post.id, post.state);
for (const t of post.targets) {
  console.log(t.platform, t.state, t.url ?? t.error);
}
```

## Step by step

1. Put the key in `POSTLAKE_API_KEY`. Use the Channels profile name exactly as in the dashboard.
1. POST with built-in `fetch` (Node 18+). No npm social packages.
1. If `resp.ok` is false, treat it as a request error. If ok, still walk `targets` for partial failures.
1. Send `Idempotency-Key` on every publish so agent or job retries stay safe.

## Read the response (don't skip this)

You get one `Post` with an overall `state` and a `targets[]` array. One entry per account. **Always check each target**; partial success is normal.

```
{
  "id": "post_a1b2c3",
  "state": "partial",
  "targets": [
    { "platform": "bluesky",  "state": "published", "url": "https://bsky.app/…" },
    { "platform": "linkedin", "state": "failed",
      "error": { "type": "invalid_request", "message": "…", "retryable": false } }
  ]
}
```

- `published`: every target succeeded. `partial`: some published, some failed. `failed`: none published. `processing`: still going (async networks like TikTok).

- **You're only charged for targets that actually publish.** Failed targets cost nothing.

- Send an `Idempotency-Key` header on writes so a retry never double-posts.

- Full detail: [Publishing](https://docs.postlake.dev/publishing) · [Errors & retries](https://docs.postlake.dev/errors)

## Where the post goes

Same rules as the docs. Pick one addressing style:

- **By profile**: `"profile": "my-brand"` posts to every account under that profile (the name on Channels).

- **Filter networks**: `"platforms": ["bluesky", "linkedin"]` narrows that set. It is a **filter, not a selector**: if you have two Pinterest boards, both match `pinterest`.

- **By account id**: `"accounts": ["acc_…"]` for exact channels (copy an id on Channels, or `GET /v1/social-accounts`).

- One profile and you omit `profile`? PostLake uses that profile. Multiple profiles and you omit it? You'll get an error that names them.

See [Publishing: where to post](https://docs.postlake.dev/publishing).

## Do more (same API)

- **Schedule**: add `scheduledAt` as UTC (trailing `Z`), or a naive local time plus `timezone` (IANA, e.g. `Europe/London`). Credits charge when it fires. [Scheduling docs](https://docs.postlake.dev/scheduling) · [scheduling guide](/guides/schedule-posts-api).

- **Media**: `POST /v1/media`, then pass the `med_…` id in `media`. [Media docs](https://docs.postlake.dev/media).

- **Per-network caption**: `textOverrides` (e.g. shorter text for X). **Per-network options**: `platformOptions` (Pinterest `boardId`, TikTok privacy, …). Live option lists: `GET /v1/platforms/{platform}`.

- **Validate first**: `POST /v1/posts/validate` runs the same checks without publishing (free).

## Pitfalls specific to this path

- Don't assume `state === "published"` means every network succeeded. Check `targets`.

- `platforms` is a filter on the profile's accounts, not a list of networks to invent.

- Async networks (e.g. TikTok) may return `processing`: poll `GET /v1/posts/{id}` or use webhooks.

Prefer an assistant over Node.js code? Point it at [MCP](https://docs.postlake.dev/mcp) (`https://api.postlake.dev/mcp`). Prefer the dashboard? Use [Quickstart → No code](https://docs.postlake.dev/quickstart).

## Common questions

### How do I post to social media with Node.js?

POST to https://api.postlake.dev/v1/posts with fetch, Bearer API key, and { text, profile }. One response covers every account on that profile. See docs → Publishing.

### Is there an npm package I need?

No package required. Native fetch is enough; PostLake is one REST endpoint for every network.

### Can an AI agent in Node use PostLake?

Yes, call the API from a tool, or connect the hosted MCP server (https://api.postlake.dev/mcp) over OAuth so the agent posts without a pasted key.

## Go deeper in the docs

These guides stay short on purpose. Canonical behaviour lives here:

    [Docs ### Quickstart Account, first channel, first post, MCP or API.](https://docs.postlake.dev/quickstart)
    [Docs ### Publishing Request body, addressing. Partial success, lifecycle.](https://docs.postlake.dev/publishing)
    [Docs ### Scheduling UTC or local time plus timezone, edit/cancel, fire-time credits.](https://docs.postlake.dev/scheduling)
    [Docs ### Platforms Limits, media rules, live platformOptions.](https://docs.postlake.dev/platforms)

Also: [Media](https://docs.postlake.dev/media) · [Errors](https://docs.postlake.dev/errors) · [MCP](https://docs.postlake.dev/mcp) · [Analytics](https://docs.postlake.dev/analytics)

## Related guides

- [Post with Python](https://postlake.dev/guides/python.md)
- [Post with LangChain](https://postlake.dev/guides/langchain.md)
- [Post with n8n](https://postlake.dev/guides/n8n.md)
- [Post everywhere at once](https://postlake.dev/guides/post-to-all-social-media-at-once.md)

[All guides](https://postlake.dev/guides/index.md) · [Full docs](https://docs.postlake.dev/) · [llms.txt](https://postlake.dev/llms.txt)

Plain markdown for agents: https://postlake.dev/guides/nodejs.md · https://postlake.dev/llms.txt