Skip to main content
CoreWeave uses API access tokens to authenticate users and grant access to resources on the CoreWeave Cloud Console. This guide explains how to create and manage access tokens on the Cloud Console for Object Storage.

Prerequisites

This guide assumes that you have an active CoreWeave account.

Create a new API access token

API access tokens authenticate programmatic access to CoreWeave services. Create them in the CoreWeave Cloud Console. To create a new access token, complete the following steps:
  1. In Cloud Console, navigate to Tokens, and then click the Create Token button in the upper-right corner.
  2. In the Create API Token dialog, complete the following fields to configure the token values, and then click Create:
    FieldDescription
    NameThe name of the token.
    ExpirationHow long the token remains valid.
    NoteA description for future reference.
  3. Select one of the following options:
    OptionDescription
    Token SecretCopy and store the token secret for use cases such as scraping metrics, scraping logs, self-hosted Grafana setup, or to add the token secret to an existing kubeconfig.
    KubeconfigCreate and download a kubeconfig for a specific cluster, so you can interact with the cluster using commands like kubectl. A kubeconfig can access multiple clusters when you switch contexts.
    Sensitive values such as token secrets and kubeconfig files are displayed in the Cloud Console modal only once, and they are never shown again after you close the modal. You must record them in a secure location.
    After you complete these steps, your new API access token is ready to use with CoreWeave services.
After creating the token, the modal presents two options: Token Secret and Kubeconfig. For AI Object Storage API access, copy and store the Token Secret, which is the bearer token you pass in Authorization: Bearer headers when calling api.coreweave.com. The Token Secret is different from the S3-compatible Access Key and secret key used for bucket operations.
If you’re connected to a Kubernetes cluster and need to retrieve an existing token secret, it’s embedded in your kubeconfig. To read it, run the following command:
kubectl config view --raw -o jsonpath='{.users[0].user.token}'
Last modified on June 4, 2026