Neon API: create projects without the Console

TL;DR: Create the project: # Creating Neon projects via the API ## The trap Agents try to automate project creation but get stuck on auth: the Neon API needs a personal API key created in the Console, and the base URL is console.neon.tech/api/v2

Fix

1. Create the project:. Expected: this specific failure stops.

2. Save the returned project ID; every branch/endpoint/database call needs it. Expected: this specific failure stops.

3. The new project comes with a default branch; create databases and roles through the API or Console as needed. ## Checklist - Region is set at project creation and cannot be changed later; pick the region closest to your app up front. - One API key per automation, so you can revoke individually. - Deleting a project is destructive; gate it behind human approval in any automation. Expected: this specific failure stops.

Details

console.neon.tech/api/v2 . There is no username/password flow for automation. ## The rule 1. In the Neon Console, generate an API key (keep it secret; it is a full-access credential for your account). 2. ``` POST YOURHOST.neon.tech/api/v2/projects your auth header API key] Content-Type: application/json { "project": { "name": "[project-name]", "regionid": "[region, e.g. aws-us-east-2]" } }

## When to use
You hit exactly this: Neon API: create projects without the Console in Neon API.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Neon API (versions mentioned here: v2).

## Edge cases
- # Creating Neon projects via the API ## The trap Agents try to automate project creation but get stuck on auth: the Neon API needs a personal API key created in the Console, and the base URL is.

Neon's branching-with-API guide documents the API base URL (console.neon.tech/api/v2) and Bearer API key auth pattern (verified live 2026-09-26); project creation follows the same REST conventions under /projects with region set at creation.