Skip to main content
Generic passthrough to the underlying hosting REST API. Naive injects the platform’s hosting credentials (token + team ID) and forwards your request, so any operation the hosting API supports can be performed against the app’s project — without you ever holding a hosting token. The upstream path goes after /vercel/proxy/. The HTTP method, query parameters, and JSON body are forwarded as-is; the upstream status code and body are returned verbatim.

Scoping Rules

Naive holds org-wide hosting credentials, so every request is validated against the app before it is forwarded: Blocked:
  • DELETE on the project itself — use DELETE /v1/apps/:id so all linked infrastructure is cleaned up together.
  • All account/team-level paths (listing projects, user info, billing, other teams’ resources) — 403 forbidden.

Methods

GET, POST, PATCH, PUT, DELETE. Request bodies must be JSON (binary uploads such as v2/files are not supported — use POST /v1/apps/:id/deploy to deploy).

Useful Operations

Consult the hosting REST API reference for the complete catalog, parameters, and response shapes.

Errors

403
Upstream errors (4xx/5xx) are passed through with their original status code and body.