yeetpostyeetpost
OverviewPlatformsAPI reference

SDKs

The API is one HTTP call with one header, so a client is a convenience rather than a requirement. Here is what exists today.

#No SDK required

Every example on these docs has a Node and a Python tab built on the standard library: fetch and urllib.request. No dependency, no version to keep up with.

curl -X POST "https://api.yeetpost.com/api/v2/posts" \
  -H "x-api-key: $YEETPOST_API_KEY" \
  -H "content-type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "text": "shipped the new api docs today",
  "connectionSlugs": [
    "linkedin",
    "x"
  ]
}'

#Node

The yeetpost package on npm predates the JSON endpoint. It wraps POST /post/{connectionSlug} and ships a CLI, so it has no fan-out, scheduling, idempotency, post listing or webhooks.

npm ›GitHub ›

For the whole v2 surface today, call the API directly. The CLI is the other option when you just want to post from a terminal.

#Coming when published

Thin hand-written clients for Node, Python and Go covering the full v2 surface, webhook signature verification included, are written but not published yet. They are not on npm, PyPI or a Go module proxy, so there is nothing to install today. When they ship, the Node and Python tabs on these docs switch to the SDK calls and this page gets install instructions. Until then the tabs stay on fetch and urllib, which is what the clients do underneath anyway.

#Generate your own

The API publishes an OpenAPI 3.1 document, so any generator will produce a client for your language. See OpenAPI.

#For agents

If the caller is an agent rather than your own code, skip the client entirely and point it at the hosted MCP server.