Database endpoints
Create another user API key
Issue another API key for a database user. Existing keys remain valid.
POST /v1/tenants/{tenant}/db/users/{username}/api-key
- Identify the database userChoose the account needing another API key.
- Issue an additional keyGenerate a credential for that user.
- Store the returned key securelyUpdate the intended application without exposing the secret.
Before you start
Use your database bearer token.
Use an identity authorized to manage access and the intended username. This creates an additional key; older keys remain valid.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
username | string | Required |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API key of the x-oc-db-user user. |
Read the result
Store the returned api_key securely. This creates an additional key for the database user; it does not invalidate older keys despite the operation's rotation name.
Response statuses
HTTP status reference
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 404 | Check the resource ID and API route. |
| 409 | Resolve the conflict before retrying. |
| 429 | Honor Retry-After when present; back off. |
| 500 | Check the outcome before retrying a write. |
| 501 | Check deployment support for this operation. |
| 503 | Honor Retry-After when present; check write outcomes. |