# How to Post to Social Media with Python (2026) · PostLake

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

Post to social media with *Python*.

Same publish contract as the docs quickstart. From Python that's one requests call. Connect accounts once in the dashboard; your code only sends text, addressing, and optional schedule/media.

**In short:** From Python, POST /v1/posts with requests (or httpx). Address a profile; read targets[]. Partial success is normal and failed targets are free.

## When this guide is for you

You're already in Python (scripts, backends, notebooks) and want social publishing without Tweepy, LinkedIn SDKs, or Meta Graph clients.

## 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 Python

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

```
import os
import requests

resp = requests.post(
    "https://api.postlake.dev/v1/posts",
    headers={
        "Authorization": f"Bearer {os.environ['POSTLAKE_API_KEY']}",
        "Idempotency-Key": "hello-python-001",  # safe retries
    },
    json={
        "text": "Hello from Python 👋",
        "profile": "my-brand",  # Channels profile name
        # Optional filter (not a selector): only these networks under the profile
        # "platforms": ["bluesky", "linkedin"],
    },
)
resp.raise_for_status()
post = resp.json()
print(post["id"], post["state"])
for t in post["targets"]:
    print(t["platform"], t["state"], t.get("url") or t.get("error"))
```

## Step by step

1. Store the key as `POSTLAKE_API_KEY` (never commit it). Use the profile name from Channels. Same string as in the [docs quickstart](https://docs.postlake.dev/quickstart).
1. POST with `requests` (or `httpx`). Omit `platforms` to hit every account on the profile; add it only to filter networks.
1. Always iterate `targets[]`. A top-level `partial` state means some networks published and some failed. Check each entry.
1. On writes, send `Idempotency-Key` so a retry never double-posts.

## 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

- `platforms` only filters accounts already on the profile. It does not create connections.

- Raise on HTTP errors, then still inspect `targets` on 200 responses with `partial`/`failed`.

- Free monthly credits exclude X publish; other networks work on the free allotment. See [pricing](/pricing).

Prefer an assistant over Python 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 Python?

Create a key and connect accounts under a profile (docs quickstart). Then POST https://api.postlake.dev/v1/posts with Authorization: Bearer sk_live_… and JSON { "text": "…", "profile": "my-brand" }. Read targets[] in the response.

### Do I need a library per social network?

No. One PostLake endpoint covers every connected network. Use requests or httpx only.

### How do I schedule from Python?

Add scheduledAt as UTC (trailing Z), or a naive local time plus timezone (IANA, e.g. Europe/London). Credits charge when it fires. See the scheduling docs.

## 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 Node.js](https://postlake.dev/guides/nodejs.md)
- [Post with LangChain](https://postlake.dev/guides/langchain.md)
- [Schedule posts via API](https://postlake.dev/guides/schedule-posts-api.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/python.md · https://postlake.dev/llms.txt