Is the API up?

The check fetches https://api.yeetpost.com/api/v2/openapi.json, the one endpoint that needs no API key. The round trip includes your own network, so treat it as a reachability signal rather than a measurement of our servers.

A green result means the API answered this browser. It does not prove that delivery to LinkedIn, X or Bluesky is healthy: a platform can be rejecting posts while our API answers every request correctly. Those failures show up per post, as a failed item with a platform error code, not here.

There is no uptime history on this page. yeetpost tracks uptime and error rates internally, and we would rather show you nothing than draw you a graph we have not published the data behind. If you need a status feed to alert on, tell us what shape it should take.

Start with the response, not this page. Every yeetpost error carries a code and, for the ones worth chasing, a req_id:

1. Read the error code against the error reference. Most failures are a bad slug, an expired connection or a platform rejection, and the code says which.
2. Check the rate limit headers. The limit is 60 requests per minute per API key, per endpoint group. See rate limits and request ids.
3. Still stuck? Send us the req_id from the response. It lets us find that exact request.