Documentation

A small API for a big pipeline

Three endpoints cover publishing, checking propagation, and rolling back. Everything else — sync, caching, failover — happens automatically.

Authentication

Every request needs a bearer token in the Authorization header. Generate one from your account settings after signing in.

auth header

Authorization: Bearer fp_live_8c1a...e42f

Endpoints

API reference

POST/v1/releases

Publish a new build. The artifact fans out to every edge node before the response returns a propagation ID.

channel string, required	Release channel, e.g. `stable`, `beta`
version string, required	Semantic version tag for this build
artifact file, required	Binary, container image, or package file to distribute
notes string, optional	Freeform release notes surfaced in the changelog feed

GET/v1/releases/:id/status

Check propagation of a release across the network.

string, required

Release ID returned from the publish call

POST/v1/rollback

Revert a channel to its previous release across the whole network.

channel

string, required

Channel to roll back

Example

Publish a release end to end

publish.sh

# push a new build to every edge node
curl -X POST https://api.fluxpoint256.com/v1/releases \
  -H "Authorization: Bearer $FP_TOKEN" \
  -F channel="stable" \
  -F version="4.2.1" \
  -F artifact=@./build/app.bin

# response
{
  "id": "rel_8f2c1a",
  "status": "propagating",
  "nodes_synced": 31,
  "nodes_total": 48
}

# poll for full propagation
curl https://api.fluxpoint256.com/v1/releases/rel_8f2c1a/status \
  -H "Authorization: Bearer $FP_TOKEN"