REST over HTTPS, JSON in and out. Every request needs your API key in the Authorization header. Sign in with your GitHub developer ID to get a key.
Pass your API key as a Bearer token on every call. Keys don't expire and aren't tied to a request volume — they're tied to the one-time purchase and your GitHub developer ID.
| Method | Path | Description |
|---|---|---|
| POST | /v1/pwa/manifest | Generate a web app manifest from your app config |
| POST | /v1/pwa/service-worker | Generate a service worker with a chosen caching strategy |
| POST | /v1/pwa/push/subscribe | Register a device for push notifications |
| GET | /v1/pwa/status/{app_id} | Check build status and current cache version |
| POST | /v1/infra/load-balancer | Provision an ALB or NLB against your AWS account |
| GET | /v1/infra/load-balancer/{id}/health | Get current target group health |
| GET | /v1/account/me | Return the GitHub developer ID tied to this key |
Send your routes and a caching strategy; get back a ready-to-deploy service worker file.
Response
Errors return a non-2xx status with a JSON body describing what to fix.
| Status | Meaning |
|---|---|
| 401 | Missing or invalid API key |
| 404 | App or load balancer ID not found |
| 422 | Malformed manifest or route list |
| 503 | AWS provisioning temporarily unavailable |
The endpoints above generate manifests, service workers and push wiring for you — these are the underlying platform references if you want to understand or hand-tune what gets generated.
The browser API our /v1/pwa/service-worker endpoint generates code against — caching, offline routing, and background events.
MDN's full PWA reference — manifests, installability, service workers, and platform APIs in one place.
What changes between a local dev server and a real HTTPS deployment — required for service workers and push to work at all.
The App Badging and Notifications APIs that sit behind the /v1/pwa/push/subscribe endpoint above.