Neon API
/api/v2/projects/{id}/auth/* endpoint removal
Deprecated, no dateSubscribe to Neon APIShare
Neon API deprecated the /api/v2/projects/{id}/auth/* endpoints without a shutdown date. Calls directed to these project-level auth paths will eventually fail once removed.
Calls it hits
/api/v2/projects/{id}/auth/*
What to use instead of these calls
Call the branch-scoped Neon Auth endpoints under /api/v2/projects/{project_id}/branches/{branch_id}/auth, covering domains, users, oauth_providers, and email_provider. Update requests to use /projects/{project_id}/branches/{branch_id}/auth/domains instead.
In Neon API's words
Deprecated. Use `/projects/{project_id}/branches/{branch_id}/auth/domains` instead.
Facts
- API
- Neon API
console.neon.tech - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Neon API's own pages
Questions
When does this change take effect?
Neon API deprecated /api/v2/projects/{id}/auth/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Neon API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Neon API 5
-
No date
GET /consumption_history/accountEndpoint removal Deprecated, no date -
No date
POST /api/v2/projects/{id}/snapshots/{id}/restoreParameter removal Deprecated, no date -
No date
POST /api/v2/projects/auth/createEndpoint removal Deprecated, no date -
No date
POST /api/v2/projects/auth/userEndpoint removal Deprecated, no date -
No date
POST /api/v2/users/me/projects/transferEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.