Update the Runtime Spec
Tune how a managed backend runs — the listening port, health check, resource requests, and replica bounds. Applies to managed and fullstack apps only; the runtime row is created when you create the app. Requires the managed_backends entitlement.
This is a partial update: only the fields you send are changed; the rest keep their current values. CPU and memory requests equal their limits (Guaranteed QoS), and the image itself is never set here — it lives on the immutable deploy so rollback stays instant.
Request body (application/json)
/healthz). Default /.min_replicas.fullstack path-routing prefixes (each /-rooted; max 20). Default ["/api"].Response (200 OK)
Returns the updated spec under runtime.
Errors
backend_paths is invalid.Get Runtime Status
Read the live runtime status of a managed backend — the running instances and the current spec. Managed / fullstack apps only. Requires the managed_backends entitlement.
Response (200 OK)
uuid. (application_id carries the same uuid string for older clients.)application_uuid, deploy_uuid (the deploy it runs), state (pending/ready/failed/terminated), ready_replicas, restart_count, and last_error. Empty when nothing is running yet.Deprecated: until the sunset the runtime spec and each instance also carries the legacy integer id and *_id fields. Don't use them; read uuid and the *_uuid fields.