Skip to content
flypod
API & library

API & library

flypod exposes a JavaScript library and a raw HTTP API, both backed by the same bearer-token auth model.

flypod has two programmatic surfaces. Both deploy to the same backend and share one auth model.

SurfaceImport / baseUse when
JS libraryimport { … } from "flypod"You deploy from Node/Bun and want types + directory helpers.
HTTP APIhttps://flypod.devYou deploy from any language, a shell, or CI with curl.

Base URL

The API host is https://flypod.dev. Deployed sites are served on a different domain: https://<id>.flypod.page, for every site, claimed or anonymous. Read the live URL out of the deploy response rather than assembling it. See Two domains, one rule.

Auth model

Authenticated requests use a bearer token:

Authorization: Bearer <token>

The token is one of two things:

TokenScopeSource
manage_tokenA single anonymous site (update, rollback, read — not delete). Once an account claims the site, only that account can manage it.Returned in the deploy response. Save it.
Account session tokenYour account; deploys are owned/permanent. Required for deletion.flypod login device authorization (the CLI also reads one from FLYPOD_TOKEN).

"Save it" applies to these two programmatic surfaces, where nothing is holding the token for you. The CLI is deliberately the opposite: it stores each site's manage_token itself and prints none, so the ownership story there is just deploy now, flypod login whenever.

There are no separate API keys. Anonymous deploys need no token. Pass an account session token to make a deploy owned and permanent. See Tokens & ownership.

Reference

On this page