Sociaro

Keys

Every request carries a key, and every key belongs to an organisation. That is what decides whose balance pays and whose logs it appears in.

Making one

Sign in at my.sociaro.com, open Keys, press Create key. Give it a name that says where it will live — production, ci, alex's laptop — because that name is what you will read later when deciding what to revoke. The console puts your organisation's name and the key's number in front of it, so a key named production is listed as Acme 3 · production, and left blank it is just Acme 3. That full name is also what our support sees, so quote it when you ask about a key.

The key is shown once. We store only its hash: if it is lost, the way forward is a new key, not recovery. Nobody at Sociaro can read it back to you, which is the same property that means nobody at Sociaro can leak it.

How long one lasts

When you create a key, Expires sets how long it works: never (the default), 30 days, 90 days or a year. It is chosen once and cannot be changed later. The Keys tab shows when it expires (UTC) next to the name, and Expired once that has passed. From then on the key is refused like a revoked one. Create a new key and switch to it before the old one runs out.

A key that expires on its own does less damage if it leaks. Give one to anything you cannot easily watch, such as a contractor's machine, a demo or a CI job.

Using one

curl https://api.sociaro.com/v1/models \
  -H "Authorization: Bearer $SOCIARO_API_KEY"

That lists every model the key may reach. A model absent from that list is a model this key cannot call, whatever the documentation says.

Revoking one

Revoke on the Keys tab stops a key immediately — anything using it fails on its next request. The key stays listed, because its past usage is part of your bill and deleting the row would not remove the spend.

Once a key is revoked you can Delete it to take it off the list. Its requests and spend stay in Spend and Logs, marked (deleted).

Revoke a key the moment it might have leaked. There is no charge for making a new one, and rotating is cheaper than wondering.

What a key can reach

Keys have no spending limit of their own. The ceiling is the organisation's balance, shared by every key it holds — so every key in an organisation reads the same figure, and any of them can read it: GET /v1/balance answers {"remaining": 312.58}. See balance and billing. One key overspending is therefore a question about the organisation, not about that key.