Better validations (fail early, not at publish time)

Hi there,

A surprisingly large portion of publishing failures has nothing to do with your code. It’s usually platform rules showing up at the worst possible moment. A post looks perfectly fine when you create it and then fails 30 seconds later when a platform finally decides it doesn’t like something.

We’ve added a bunch of additional validations so more problems are caught when you create the post, not when it’s already being published.

Some examples:

Placement validation

Facebook and Pinterest now require explicit placement identifiers (page_id or board_id). Previously the platforms sometimes defaulted to something implicitly, which could lead to “oops, wrong page” situations. Now we ask for it upfront.

If you’re unsure about available placements, you can fetch them via the API:
https://postproxy.dev/reference/profiles/#list-placements

Visibility parameters

For TikTok and YouTube we now validate visibility parameters before publishing. Without them the platforms simply refuse the post later, so it’s better to catch it early.

Text length validation

When cross-posting to multiple platforms, one platform may accept a text while another rejects it because it’s too long. We now detect those cases and warn you immediately.

All these validations happen when you submit the post to /api/posts, not later during platform execution. This makes failures predictable and easier to debug.

More details about the Posts API here:
https://postproxy.dev/reference/posts/

The goal here is simple:
Publishing should be boring. Errors should be obvious. And surprises should be rare.

If you hit a platform rule we still don’t validate yet, tell us. Chances are we’ll add it.

Best,
Dmitry