Skip to content

Create a console API key and select account context

Authenticate customer API requests without confusing service or application credentials.

Published on Oct 12, 2026

Before you start

Sign into your own customer account. API keys can expose account resources and must be treated as secrets.

Steps

  1. Open API keys in Developer tools and create a key with the intended name and available scope/expiry settings.
  2. Copy it into your secret manager at creation time and keep it out of source control, URLs, screenshots, and support tickets.
  3. Use Authorization: Bearer with the customer API key for console API requests.
  4. Set X-Account-ID for a specific account you belong to when your user has multiple memberships.
  5. Start with a read-only account or service request. Revoke unused or exposed keys and update your clients.

Check the result

The authenticated API lists only resources the user can access in the selected account.

Troubleshooting

401 indicates an authentication problem; 403 can mean account or permission denial. A GPU application token, object-storage secret, and console API key serve different systems.

Next steps

Last updated October 12, 2026. Availability and prices are shown in the console before checkout.
Still need help? Open a support ticket with your service name, the time of the issue, and a redacted error message. Never include passwords or API keys.
Categories
Billing and support CLI and developer tools DocVault AI GPU Cloud GPU applications Getting started Hosting and DNS Managed AI APIs Object Storage VPS
Products
DocVault AI GPU Object Storage Shared Hosting VPS