Overview
API keys let you authorize requests to Uniskai from your own scripts. A common use is pushing external cost data into Uniskai, but the same key can also be used to authorize other Uniskai API requests. You create and manage your keys on the Api-Keys tab of your account, where you can generate a new key, see your existing keys, and revoke a key you no longer need.
How it works
Each API key is used to authorize your script's requests to Uniskai. The key is passed in the request's Authorization header in the form Api-Key <your_key>.
headers = {
'Authorization': f'Api-Key {api_key}',
'Content-Type': 'application/json',
}A key has two parts: a short prefix and a secret part. In the Api-Keys table only the prefix is shown (masked), never the full key.
The full key value is shown only once, at the moment you generate it. Uniskai stores the key only as a secure hash, never in plaintext, so it cannot be shown to you again later. If you lose it, generate a new key.
Example: pushing billing data
To push external cost data, send a POST request with your API key in the Authorization header and the billing data in the request body.
Request:
POST /api/organizations/<org_id>/external-costs/push
Authorization: Api-Key <your_key>
Content-Type: application/json
{
"billing_period": "2026-07",
"rows": [
{
"ServiceName": "My-External-Vendor",
"BilledCost": 100,
"BillingCurrency": "USD",
"BillingPeriodStart": "2026-07-01T00:00:00Z",
"BillingPeriodEnd": "2026-08-01T00:00:00Z",
"ChargePeriodStart": "2026-07-01T00:00:00Z",
"ChargePeriodEnd": "2026-07-02T00:00:00Z"
}
]
}
billing_period— the billing month inYYYY-MMformat.rows— a non-empty list of cost rows. Each row must includeBillingPeriodStart.
The request is accepted and processed in the background; the pushed data then appears in your cost dashboards.
Prerequisites
You are signed in to Uniskai.
To confirm: the role/permission required to view the Api-Keys tab and generate keys.
Step-by-step
1. Open the Api-Keys page
Click your user avatar in the top-right corner.
Select Profile.
On the My account page, open the Api-Keys tab.
You will see the API Keys table with the columns Label, Prefix, Last used, Created, and a Revoke action for each key.
2. Generate a new key
Click + Generate new key.
In the Generate new API key dialog, optionally enter a Key label (for example, a name that helps you recognize where the key is used).
Click Generate.
3. Copy and store the key
A confirmation appears (API key generated) and the Copy your new API key dialog shows your full key.
Copy the key using the copy icon.
Click I've copied this key.
The dialog warns Copy this key now — it will not be shown again. Save the key in a secure place before closing the dialog.
The new key then appears as a row in the table with its masked prefix, Last used = Never, and the Created date.
4. Revoke a key
In the table, click Revoke on the key you want to remove.
In the Revoke this key? dialog, confirm by clicking Revoke.
The dialog warns Scripts using this key will stop working immediately. Revoking takes effect right away.
A confirmation appears (API key revoked) and the key is removed from the table.
Results
A generated key is listed on the Api-Keys tab and can be used in your scripts to push external cost data into Uniskai.
A revoked key stops working immediately and no longer appears in the table.
Key notes and limitations
The full key is shown only once, at generation. It cannot be retrieved later.
The table shows only the masked prefix, not the full key.
Label is optional — you can leave it empty, and the key is created without a name (the Label column shows a dash).
A key's Label cannot be edited after the key is created.
Revoke is immediate and cannot be undone; any script using that key stops working.
You can create a maximum of 3 API keys.
Key rotation is your responsibility — generate a new key and revoke the old one periodically.
Items to confirm
Role/permission required to access Api-Keys and generate/revoke keys.