SDKs Overview

Every client here is a thin wrapper over the REST API. The platform APIs, formatting, media handling, retries, and scheduling all run on our side, so an SDK stays small and gains new networks without you upgrading anything.

Your app  →  SDK  →  api.fopost.com  →  the networks

Cloud clients

These talk to your FoPost account with an API key.

All of them are MIT licensed and open source. All are 0.x, so pin an exact version if a breaking minor would hurt.

Framework integrations

Each one wraps the client for its language and adds the wiring that framework expects: configuration, dependency injection, background jobs, console commands, and a signature-verified webhook endpoint. None of them adds to the API surface, so the language SDK's page stays the reference for resources and errors.

Automation & tooling

For publishing from somewhere that is not your application code.

Zapier and Make review custom apps by hand before they appear in a public directory, and both integrations are private apps until that happens. Their pages say how to install one today.

Another language

The REST API is plain JSON over HTTPS with one header, so a language with no official client is still one request away:

curl -X POST https://api.fopost.com/v1/posts \
  -H "X-API-Key: $FOPOST_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workspace_id": "7d2b8c11-4e5a-4a8f-b0d9-3c5e6f7a8b90",
    "accounts": ["3a9f1d20-6c77-4b2e-9a01-8f5d2c3b4e10"],
    "content": [{ "text": "Hello from anywhere." }]
  }'

The OpenAPI spec generates a usable client in most languages. If you want an official one for a language that is missing, tell us which; demand is how the order gets decided.

Not the self-hosted library

There is a separate, free PHP library that talks to each network from your own server with your own app credentials. It is not part of the Cloud and is documented in its own repository; everything on this page publishes through your FoPost account instead.

Next