Authenticate to the Deno Deploy v2 REST API and list an organization's apps

Documented steps

1. Auth: Bearer token: create an access token in the console.deno.com dashboard settings, send Authorization: Bearer <token> on every request to https://api.deno.com.
2. Create an API access token from the Deno Deploy dashboard (console.deno.com) - tokens are created via the UI; there is no self-serve token-creation API endpoint.
3. Use base URL https://api.deno.com with the current v2 API. Do NOT use the legacy Subhosting v1 API (api.deno.com/v1/), discontinued July 20, 2026.
4. List apps: GET https://api.deno.com/v2/apps with cursor-based pagination (cursor/limit query params; Link response header points to the next page).
5. Fetch one app: GET https://api.deno.com/v2/apps/{appId} (UUID or slug).
6. The machine-readable spec is at https://api.deno.com/v2/openapi.json; human docs at https://api.deno.com/v2/docs.
7. v2 renames v1 concepts: 'organizations/projects/deployments' became 'apps' and 'revisions' - do not mix endpoint shapes between generations.
8. Official docs: https://docs.deno.com/deploy/api/rest/ ; https://api.deno.com/v2/openapi.json ; https://docs.deno.com/deploy/reference/organizations/