Better error messages (with actual context)

Hi there,

When something fails, the only thing that matters is: can you understand what happened and fix it quickly?

A lot of platform APIs don’t help with that. They return cryptic messages, inconsistent codes, or responses that technically make sense but don’t explain much in practice.

We’ve reworked how errors are surfaced in Postproxy to make them more useful.

When a post fails, you now see:

• the original platform error

• platform error codes and subcodes

• a readable explanation of what happened

• and, when we know the pattern, a Postproxy tip on how to fix it

For example, instead of just getting a generic media error from Instagram, you’ll also see a hint about file size limits if that’s the likely cause.

All of this is also available in the API response. Error details are structured and include fields like:

• error

• error_details.platform_error_code

• error_details.platform_error_subcode

• error_details.postproxy_note

So if you’re building your own dashboards or automation on top of Postproxy, you can surface the same level of clarity to your users.

We can’t prevent every failure. Platforms behave the way they behave. But we can make sure you’re never left guessing what went wrong. If you run into an error that still feels unclear, send it over. Those are exactly the cases we want to improve next.

Cheers,
Dmitry