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.
| Surface | Import / base | Use when |
|---|---|---|
| JS library | import { … } from "flypod" | You deploy from Node/Bun and want types + directory helpers. |
| HTTP API | https://flypod.dev | You deploy from any language, a shell, or CI with curl. |
Base URL
The public host is https://flypod.dev. Deployed sites are served at https://<id>.flypod.dev.
Auth model
Authenticated requests use a bearer token:
Authorization: Bearer <token>The token is one of two things:
| Token | Scope | Source |
|---|---|---|
manage_token | A single site (update, rollback, read — not delete). | Returned in the deploy response. Save it. |
| Account session token | Your account; deploys are owned/permanent. Required for deletion. | flypod login device authorization. |
"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.
Anonymous deploys need no token. Pass an account session token to make a deploy owned and permanent. See Tokens & ownership.
Reference
Library
The flypod npm package: deploySite, collectDist, resolveDeployDir, and the DeployOptions / DeployResult types.
TypeScript demo
A runnable example. Download and deploy a folder in two calls, or check it inline.
HTTP API
REST endpoints for deploy, redeploy, rollback, and account management, with curl examples.
flypod token
Reveal the manage token for a site you deployed, for the rare case where you need to act on it from a machine that doesn't remember it.
Library
The flypod npm package deploys a folder of static files to a live URL from Node or Bun. Reference for deploySite, collectDist, resolveDeployDir, and the DeployOptions / DeployResult types.