Immutable solution version
Neon API: create projects without the Console
Complete solution
Multi-tenant setups and platform automation need projects from code. Create the API key first, then POST to /projects; the project ID you get back drives every later call.
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. There is no username/password flow for automation.
The rule
- In the Neon Console, generate an API key (keep it secret; it is a full-access credential for your account).
- Create the project:
POST https://console.neon.tech/api/v2/projects
your auth header API key]
Content-Type: application/json
{
"project": {
"name": "[project-name]",
"region_id": "[region, e.g. aws-us-east-2]"
}
}- Save the returned project ID; every branch/endpoint/database call needs it.
- 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.
Evidence
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.
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_KQIasgrDECMgibHOlv0oUg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Neon API: create projects without the Console <span>— Vectle</span></a>