Skip to main content

Create a key

1

Sign in

Sign in at app.sixtyfour.ai. New accounts create an organization during onboarding.
2

Open API Keys

Open API Keys in Settings. The page shows the keys of your active team; switch teams to see another team’s keys.
3

Create the key

Click Create key, enter a name and set the expiration, then confirm.
4

Copy the key

Sixtyfour shows the full key once. Store it in a secret manager or environment variable. Sixtyfour cannot show it again.
Send the key in the x-api-key header.
HTTP 202 returns a Job:
Poll GET /v1/jobs/{job_id} after next_poll_after seconds until succeeded, failed or canceled. See Async Jobs. Keys start with api_. See Authentication for OAuth tokens and how the API picks a credential.

Team scope

Every key belongs to one team. Requests made with the key draw on your organization’s credits and count toward the team’s monthly credit limit, if it has one. The workflows, runs and logs they create belong to that team. A key sees the team’s work, so creating one takes belonging to the team. Organization admins and owners can add themselves to any team first. See Roles and Permissions for how organization and team roles work.

Expiration

The keys table shows each key’s expiry date, or Never. Expired keys stop authenticating. Create a replacement before the expiry date and rotate your services to it. Sixtyfour emails a key’s creator once before the key expires, whether or not the key is in use. If the key’s creator has left your organization or can’t receive email from us, for example because their address bounced, your organization’s admins get the warning instead. Admins can send security notices to chosen teams or people under Notifications in Settings, and set them back to their default recipients there.

When a key’s owner leaves

A key acts as the person who owns it, at first whoever created it: in its team, it sees the private runs and usage that person can see. When they leave the team or the organization, the key keeps working and goes to an admin of its team: whoever has been on the team longest of its owners and the organization owners and admins on it. That admin gets an email, and the keys table tells them why the key is theirs. If nobody on the team is an owner or admin, the key stays with the person who left, and the keys table marks it No longer on this team or No longer in the organization until a team owner or admin who joins the team takes it. A team owner, or an organization admin on the team, can hand a key that came to them, or one whose owner left, to anyone on the team from the keys table. It is theirs at once, and they get an email. From the key’s next request it acts as its new owner, and its usage from then on counts as theirs; usage from before stays with the earlier owner. The audit log records every handover.

Revoke a key

Revoke a key under API Keys in Settings. A revoked key stops working within five minutes; see Revocation and expiry. Revoking a key pauses schedules that use it; resume them with a working key.

Keep keys safe

  • Keep keys server-side. Never ship them in browser or mobile code.
  • Use one key per service so you can revoke one without affecting the others.
  • Prefer OAuth clients for machine-to-machine integrations that need short-lived tokens.
For the original routes, see Legacy.