Apps · 4 November 2026

Render API for Apps

The web service endpoints of Render's REST API are served under /compat/render/v1, so Render API clients and the render CLI manage Apps by changing only their host (RENDER_HOST) and API key (Authorization: Bearer <key>). Supported: create an image-backed web service (POST /services, type web_service, runtime image), list, get, update its name, image, plan and health check path, scale (POST /services/{serviceId}/scale) and delete. Lists return [{"cursor", "service"}] and are paginated with cursor and limit (20 by default, at most 100), and can be filtered by name. The plans starter (the default), standard, pro, pro_plus, pro_max and pro_ultra create an App with 1, 1, 2, 4, 4 or 8 vCPUs and 0.5, 2, 4, 8, 16 or 32 GiB of memory, billed by measured use; each copy serves on port 10000, Render's default PORT. Errors return Render's status codes and {"id", "message"} body. A field or operation Apps does not support yet, such as repo or deploys, returns 400 or 404.