API keys
Programmatic access for scripts, integrations, and external services
API keys let scripts, services, and third-party integrations talk to Looped on behalf of your company. Every key is scoped to a single company and a set of permissions.
The API keys page is for Owners and anyone whose Company role includes "Manage API keys" (the Admin role does). Open it from Settings → API Keys.
Creating a key
- Click Create API Key.
- Give it a memorable name — "Zapier production", "Reporting service", "Joe's laptop". The name only matters to you.
- Pick its permissions: a role in each app the key needs, or specific permissions.
- Optionally set an expiration date. After that date, the key stops working. Leave empty for non-expiring keys.
- Click Create.
A success screen appears with the raw key — it starts with looped_. Copy it now. Once you close that screen, the key cannot be retrieved (we only store its hash). If you lose it, revoke it and create a new one.
Hand the key to the integration that needs it (their dashboard, your company's secrets manager, an .env file, whatever).
Permissions
A key holds permissions directly. For each app the API reaches (Company, Track, Invoices, Financials and Inventory) you pick Read-only, Full or Specific permissions, and with Specific permissions you tick exactly what the integration needs.
A key can't do more than the person who makes it. Roles and permissions your own role doesn't include are greyed out, and the API refuses them too. A key also never gets billing or the right to manage other API keys.
On the wire each permission has a name like track:time.write ("Log own time") or invoices:invoices.send ("Send invoices"). GET /v1/whoami lists a key's permissions, and a 403 names the permission that was missing.
Keys made before September 2026 held coarse scopes such as write:time. They keep working with exactly the access they had: Looped reads each old scope as the permissions it covered, and the key's details show those permissions. Creating a key through the API with the old scope names still works too, but it's deprecated.
Using a key
Send the key in the X-API-Key header on every request to https://api.looped.sh:
curl https://api.looped.sh/v1/invoices \
-H "X-API-Key: looped_..."The key carries the company scope — you don't pass teamId separately. The full endpoint reference lives at api.looped.sh (interactive Scalar UI) or api.looped.sh/openapi.json (machine-readable).
Editing a key
To rename a key or adjust its permissions / expiration:
- Click the ⋯ menu on the key's row → View Details.
- Click Edit.
- Change the name, permissions or expiration.
- Save Changes.
The key value itself does not change — your integration keeps working with the same looped_... value.
Revoking a key
Revoking immediately invalidates the key but keeps the row around so you can audit which key did what later. Use this when a key is leaked or rotated.
- Click the ⋯ menu → Revoke Key.
- Confirm.
The badge flips from Active to Revoked and any further calls return 401.
Deleting a key
Deleting removes the row entirely. Use this for keys created in error or that you don't need to keep on record.
- Click the ⋯ menu → Delete Key.
- Confirm.
The key disappears from the table.
Status badges
| Badge | Means |
|---|---|
| Active | Authenticates successfully |
| Expired | Past its expiration date. Edit it via View Details to set a new expiration if you want to reactivate, or delete it |
| Revoked | Manually revoked. Cannot be reactivated — create a new key |
Last-used timestamp
Each key shows a "last used" relative timestamp on the table. Useful for spotting keys that haven't run in months — candidates for cleanup.
Best practices
- Give each integration its own key. Don't share a single key across services. Easier to rotate and audit.
- Give a production key only the permissions its integration uses. Picking specific permissions is usually tighter than a whole role.
- Set expirations on keys you'll only need temporarily (e.g. a one-off migration script).
- Rotate keys periodically — every 90 / 180 days is a sensible default for production integrations.
- If you suspect a leak, revoke first, ask questions later.
Are you an AI? Visit llms.txt — these docs as plain markdown.