Accounts, teams and API keys

An account holds your plan, credits, API keys, tasks and webhook settings. People reach it through the dashboard, as its members.

There are no passwords. Enter your email on the sign-in page and we send you a link. The link works once and expires after 15 minutes; signing in also spends any older links sent to the same mailbox. If you open it on a different device from the one that asked for it, the dashboard asks you to confirm the address first. When the sign-in page shows Continue with Google, you can also sign in with a Google account whose email Google has verified. A session lasts 30 days.

Addresses that reach the same mailbox, such as a +tag variant or a Gmail address with dots, sign in as the same user. Disposable email addresses are refused.

Your first sign-in creates your user and an account of your own on the Free plan, with you as its owner, named after your address. You join other accounts by invitation. If you belong to more than one, switch between them with the account picker at the top of the dashboard.

The Free plan has one seat, so a Free account has room for its owner only. Paid plans have unlimited seats. Members and pending invites both count toward seats.

Members and roles

Each member of an account is an owner or a member.

Action	Owner	Member
See the overview, usage, tasks, key list, team, pending invites and webhook delivery log	Yes	Yes
Leave the account	Yes	Yes
Create and revoke API keys	Yes	No
Invite people, revoke invites, change roles, remove other members	Yes	No
Change the plan and open the billing portal	Yes	No
See and rotate the webhook signing secret, send test deliveries, redeliver	Yes	No
Open the referrals page and submit bonus claims	Yes	No
Read the audit log	Yes	No

Owners change roles on the Team page with Make owner and Make member. This is also how you hand an account on: make the other person an owner, then leave or make yourself a member. An account always keeps at least one owner, so a change that would leave it with none is refused.

Owners remove any member, other owners included, with Remove. Any member can leave with Leave on their own row. When someone leaves or is removed, the API keys they created are revoked and the invites they sent that are still pending are deleted. An owner who is made a member also loses their pending invites.

Invites

Owners invite people on the Team page with an email address and a role, Member or Owner. We email the invite link. An invite expires after 7 days. Pending invites are listed with their role and expiry date, and owners can cancel one with Revoke: its link stops working and its seat is freed.

Inviting an address that already has a pending invite replaces it, and the earlier link stops working.
Inviting someone who is already a member is refused.
A pending invite holds a seat until it is accepted, revoked or expires.
An account can send up to 20 invites an hour.

To accept, open the link and sign in with the invited address, or another address of the same mailbox. If you are signed in with a different address, the dashboard shows which address the invite was for, partly masked, and offers Sign out and continue. A link that was used, revoked or has expired cannot be accepted, and neither can an invite whose sender is no longer an owner. Ask an owner to send a new one.

API keys

Owners create keys on the API keys page: type a name of 1 to 100 characters, such as production, and click Create key. The full key is shown once, right after it is created, so copy it then. After that the page shows the key's name, its first characters, when it was created and when it was last used. Members see the list but cannot create or revoke keys.

One key works for every endpoint; keys have no scopes. Every key spends the account's credits. An account can have up to 50 active keys; revoke one to create another. See Authentication for how to send a key.

Revoke stops a key within a minute. Revoked keys stay listed under Show revoked.

A key is tied to the person who created it. When that person leaves the account, is removed, or deletes their user, every key they created is revoked. Before someone leaves, move your services to a key created by an owner who is staying.

To rotate a key without downtime:

Create a new key.
Deploy it everywhere the old key is used. Both keys work in the meantime.
Wait until the old key's Last used time stops changing. It can lag by up to a minute.
Revoke the old key.

Audit log

Owners read the account's history on the Audit log page and can filter it by action. Each event shows when it happened, who acted (a user, our operators, Stripe or the system), the action, its target, the client IP where one was recorded, and details. Events are kept for 400 days. The log records:

sign-ins, Sign out everywhere and deleted users;
API keys created and revoked;
invites sent, accepted and revoked, members removed or leaving, and role changes;
webhook secret rotations, test deliveries and redeliveries;
bonus claims and their review;
completed checkouts and subscription changes;
changes our operators make to the account's plan, limits and credits.

Your data and sessions

Download my data on the Settings page (GET /me/export) gives you personal-data.json. It holds:

your user: id, email address and when it was created;
the accounts you belong to, with your role in each;
your sessions, with when each started and expires;
the notification emails sent to you;
for each account you own: its plan and billing details, API keys (name, first characters and dates), members, invites, bonus claims, referral commissions and daily usage by engine.

It never contains API keys, session tokens, invite links or the webhook signing secret. You can download it 5 times an hour.

Sign out everywhere on the same page ends every session of your user on every device, this one included. API keys keep working.

Deleting your user or an account

Delete account on the Settings page deletes your user. Type your email address to confirm. This cannot be undone.

You leave every account you belong to.
An account where you are the only member is deleted with you. Its queued tasks are dropped, its API keys stop working, and a paid subscription is cancelled at once, without a refund for the rest of the billing period.
An account with other members stays. If you are its only owner, make another member an owner first; until then the deletion is refused.
In accounts that stay, the keys you created are revoked and the invites you sent that are still pending are deleted.
Your address is removed from the audit logs and notification records of your accounts.
30 days after an account is deleted, its name, invite addresses and bonus claim links are erased and its keys and audit events are deleted. Records of credits charged and amounts billed are kept.
If you sign up again with the same mailbox, the new account starts without free credits.

There is no separate button to delete an account. An account is deleted when its last member deletes their user. To close an account that has other members, or to close one without deleting your user, an owner can email [email protected].