API Keys

API Keys page showing Your API Keys table with four keys for Team Acasia: Test 3, nelsondevsquad, Test key2, and Test key, each with masked key value, created date, last used timestamp, and actions menu

API keys are scoped to the active organization and authenticate requests to:

Inference endpoints
Automated workflows and pipelines
Acasia service integrations

API key table fields

Field	Description
Name	Label you assigned to the key
Key	Masked key value — the full key is only shown once at creation
Created	Date the key was created
Last Used	Timestamp of the most recent authenticated request
Actions	Revoke or copy the key

Creating an API key

Click Create API Key

Opens the key creation panel.

Name the key

Use a name that identifies the application, environment, or owner — for example: production-app, dev-pipeline, or team-acasia.

Copy the key immediately

The full key value is shown only once at creation. Copy it and store it in your secrets manager before closing the panel. It cannot be retrieved again.

API keys are shown in full only at the time of creation. If you lose a key, you must revoke it and create a new one. Never commit API keys to source code or share them in plaintext.

Using an API key

Include the API key in the Authorization header of requests to Acasia endpoints:

curl https://<your-endpoint-url>/v1/chat/completions \
  -H "Authorization: Bearer <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{"model": "<model>", "messages": [{"role": "user", "content": "Hello"}]}'

const response = await fetch(process.env.ACASIA_ENDPOINT_URL, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.ACASIA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    model: process.env.ACASIA_MODEL_NAME,
    messages: [{ role: "user", content: prompt }],
  }),
});

Last Used timestamp

Use this column to confirm a key is actively used, identify stale keys, and audit usage across your organization.

Rotating and revoking keys

Rotate a key by creating a new one, updating your application to use it, then revoking the old one. Revoke a key from the Actions menu. Revocation is immediate.

Action	When to use
Rotate	Periodic security rotation, suspected exposure, team member offboarding
Revoke	Key is no longer needed, confirmed exposure, decommissioning an application

Revoking a key immediately invalidates it. Confirm no active applications or workflows depend on the key before revoking.

Best practices

Name keys by application, environment, or owner
Store keys in a secrets manager
Rotate keys periodically and whenever a team member with key access leaves
Revoke keys immediately if exposure is suspected
Never commit keys to source code or include them in logs
Review the Last Used column regularly to identify and remove stale keys

Cloud

Marketplace

API key table fields

Creating an API key

Using an API key

Last Used timestamp

Rotating and revoking keys

Best practices

​API key table fields

​Creating an API key

​Using an API key

​Last Used timestamp

​Rotating and revoking keys

​Best practices

API key table fields

Creating an API key

Using an API key

Last Used timestamp

Rotating and revoking keys

Best practices