Use cases

For content repurposing

One idea, nine places, without nine copies of the same code.

The problem

The same post rarely works unchanged everywhere. X wants it short, LinkedIn wants it longer, TikTok will not take text at all. So repurposing turns into a per-network fork in your code, and the fork is where the bugs live.

What PostLake does about it

One call, many destinations

Send once, address several accounts, get a per-network result back.

Per-network overrides

Override the caption or the media for a single network without duplicating the post. The shared version covers the rest.

Limits checked per network

A caption that fits LinkedIn and not X is caught before anything is sent, with the exact overspill named.

Partial success is visible

If eight networks publish and one refuses, you see exactly which and why, rather than one ambiguous failure for the lot.

How it fits together

Post once with an accounts array, add textOverrides or mediaOverrides only where a network needs something different.

curl -X POST https://api.postlake.dev/v1/posts \
  -H "Authorization: Bearer $POSTLAKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "…", "accounts": ["acc_…"]}'

Common questions

Can I post different text to different networks in one call?

Yes. Send the shared text, then override it for the networks that need something else. Anything without an override uses the shared version.

What if one network rejects it?

The others still publish. The response names the one that failed, why, and how to fix it, and you are not charged for it.

Can I reuse the same media everywhere?

Yes. Upload once and reference the same media id across every network, with overrides only where a network's rules differ.

Related