Updating organization API page for org keys and new endpoints

[bgrenon]

Preview:
https://neon-next-git-bgrenon-org-api-keys-neondatabase.vercel.app/docs/manage/orgs-api

This is written assuming the future state:

/{org_id} is only needed when using personal API keys

It's removed from most examples on this page, which use the org API key. @kszafran if this assumption is incorrect, let me know and I'll modify accordingly.

Note: I was unable to remove a member . All other endpoints I had no issues with.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
neon-next	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2024 5:14pm

[kszafran]

There will be a couple of endpoints that won't be supported by org API keys for GA, even though you'd expect them to (e.g. creating an org invitation). I'll give you a list later, for now we could add some comment (like "currently not supported when called with an organization API key") for:

• createOrganizationInvitations — POST /organizations/{org_id}/invitations
• removeOrganizationMember — DELETE /organizations/{org_id}/members/{member_id}
• deleteOrganization — DELETE /organizations/{org_id}

[bgrenon]

Annotations added, except for:

• deleteOrganization — DELETE /organizations/{org_id}

This endpoint is not exposed in the public docs (it's still behind the frontend tag).