---
title: "Discussion on \"Why \"the API returned 200\" isn't proof your post is live\" | Hashnode"
description: "Discussion on \"Why \"the API returned 200\" isn't proof your post is live\". I build LazyRelay, a social scheduling tool. Something that became obvious once we started looking closely: a successful API response from a social platform does not mean your content is actually visi"
url: "https://hashnode.com/posts/why-the-api-returned-200-isn-t-proof-your-post-is-live/6a91a661dbc161a40be59d38"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why "the API returned 200" isn't proof your post is live](https://lazyrelay.hashnode.dev/why-the-api-returned-200-isn-t-proof-your-post-is-live?utm_source=hashnode&utm_medium=feed)

I build LazyRelay, a social scheduling tool. Something that became obvious once we started looking closely: a successful API response from a social platform does not mean your content is actually visi

Aug 28 · 3 min read · lazyrelay.hashnode.dev  
Read the article

-   [#webdev](https://hashnode.com/tag/webdev)
-   [#api](https://hashnode.com/tag/api)
-   [#javascript](https://hashnode.com/tag/javascript)

## Written by

[Werner Goss](https://hashnode.com/@wernergoss)

@wernergoss

  
[View profile](https://hashnode.com/@wernergoss)

Building LazyRelay, a social scheduling tool that verifies posts are actually live, not just accepted.

Building LazyRelay, a social scheduling tool. I write about the gap between an API call succeeding and content actually going live.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
