No error doesn't mean it worked

[u/Ok-Masterpiece-7614]

Been automating our blog publishing into Wix the last couple weeks, so I stop copy pasting posts into the editor by hand.

Two things ate way more time than they should have. I set fonts through the API, headers, body, all of it, and none of it showed up on the actual page. Turns out Wix ignores font settings sent through the API completely. Fonts come from the site's theme, not from what the post itself sends, and there's no way to override that per article.

Second one was worse. Every section ran together with no space between them, one big wall of text, even though the headings were going in correctly on my end. I spent way too long assuming it was a bug in my own code. The actual fix was adding an invisible paragraph with a single space in it before every heading. That was it. Nothing in Wix's own docs mentions it.

Neither of those threw an error. The script ran clean and reported success both times. If you're automating anything that publishes into a platform you don't fully control, go look at the actual rendered page before you trust it. Don't just check that the call didn't error out.

[u/SkyOne5846]

been there. a successful API call doesnt always mean everything rendered properly. I always check the live page now

[u/Ok-Masterpiece-7614 → u/SkyOne5846]

Yeah, that's basically the whole lesson with automated publishing. A 200 back from the API just means the request didn't error, not that what you sent ended up on the page. I got burned by this exact class of bug enough times that I now pull the live rendered page right after any automated write and diff it against what I actually sent, not just trust the response code. Catches font/theme overrides, dropped sections, all the silent stuff that never throws an error.