Every operation of the Apps API, under /deploy/api. Sign requests with an access key (Authorization: EWS-ACCESS-KEY <id>:<secret>). A successful JSON response is { "success": true, "data": … }.
Deployable applications: what runs, how it is checked, where it is served
Pooled hosting of a Next.js app: hand over a build, see where and how the app runs (scales to zero)
A pooled app's Postgres on its pool host: single node, no failover, backed up daily and before a delete
Rollouts of an app: trigger, read, wait for, cancel
Environment of an app: plain values, secrets, synced 1Password references
How each database and cache binding connects — everything but the password
Roll the saved configuration out
Managed Postgres binding — DATABASE_URL and PG* generated from it
Managed Valkey binding — REDIS_URL and VALKEY_URL generated from it
Managed Kafka binding — KAFKA_BOOTSTRAP_SERVERS and the SASL settings, as a named user
Managed RabbitMQ binding — AMQP_URL and AMQP_HOSTS, as a named user
Document Database binding — MONGODB_URL, as the master user or one of its users
Error Tracking binding — SENTRY_DSN, NEXT_PUBLIC_SENTRY_DSN, SENTRY_ENVIRONMENT, SENTRY_RELEASE and a per-build upload token
Scheduled jobs (cron) of an app: a command run on a schedule in the app’s image
Pull credentials for external registries (ghcr.io, Docker Hub, any v2 registry)
Custom domains of an app
Generated from the API description, the same one the API checks requests against and the CLI is built from.