Access credentials¶
Use access credentials to call the CloudSigma AI Studio API. On the Access credentials page, you can create personal access tokens and manage application identities available to your account.
Access credentials identify the caller. Product permissions and workspace roles determine which products, models, workspaces, and resources the caller can access.
In the console, open the account menu in the upper-right corner and select Access credentials.
Choose a calling identity¶
Call as yourself: Use a personal access token. Requests use the current user’s permissions in the target product. This option is suitable for local development, personal scripts, CLI debugging, and BI direct connections.
Call as an application: Use a service account. A service account is an application identity independent of a personal account and requires its own product permissions. This option is suitable for backend applications, CI/CD, and long-running automation.
Supported products and access methods¶
Product |
Service |
API |
Credentials |
|---|---|---|---|
AI Studio |
Manage resources in workspaces |
Personal access token |
API endpoint: Use the regional API base URL for the region that contains the target workspace. For Manila 2 (
mnl2), usehttps://genai.mnl2.cloudsigma.com/v5.Workspace: Operations on a workspace require its workspace ID and a corresponding workspace membership and role.
Service accounts and credentials¶
Use a service account for an application or automation when this option is available to your account. It does not inherit the creator’s personal permissions. Select a workspace and assign the service account a role in that workspace.
A service account uses the following credentials:
Client ID and Client Secret: Use them together to obtain an access token through OAuth. Set the expiration for each Secret separately and rotate it before it expires.
Use credentials securely¶
The page displays a complete token, Client Secret, or API Key only when you create or update it. Copy and store the value before closing the dialog.
Store credentials in server-side environment variables or a secret manager. Do not put them in source code, client-side code, logs, tickets, or screenshots.
If a credential is exposed, disable or delete it, create a new credential, and replace the old value stored by the application.