Skip to content
Docs menu

Guides

Features

API

Integrations

Team, API keys and billing

Who on your team can do what, the keys your apps send with, and the plan that keeps your email flowing.

Team

Under Team, the account's owners add people, set their roles and remove them.

The Add a teammate form under Team, with fields for name, email address and role, and a Send invitation button

Someone new to Wakio gets an email with a link to choose a password. Someone who already has a Wakio login is added right away and gets an email saying so.

The Team list, with Maya Okafor as an active owner and Jordan Lee as a member whose status reads Pending
  1. Pending means they have not accepted yet. Choose Resend to send their invitation again.

Each person has one role: Owner, Admin or Member.

  • Owners can do everything, and are the only people who see Billing, manage the team, or change the account's settings. An owner can change anyone else's role or remove them, but not their own. To step down, ask another owner to change your role.
  • Admins run the day-to-day sending: they add and check sending domains, issue and revoke API keys, create and send campaigns and flows, and manage lists, imports and forms.
  • Members can see the account's pages, including Team, Deliveries, contacts and campaigns, but cannot change them.

Whatever their role, everyone changes their own name and password in Settings.

API keys

An API key is the password an app uses to send email through Wakio. Under API keys, every role can see the account's keys, and owners and admins can issue and revoke them.

Wakio shows a new key once, when you issue it, so copy it right away. Revoking a key stops it working at once, so issue the replacement first if an app still uses it. Your developer can read how keys work in the API overview.

Billing

Only owners see Billing. It shows your plan, how much of this month's allowance you have used, and where you are heading by the end of your billing period.

The Billing summary for the Scale plan at $499 a month, with 187,716 of 500,000 sent this cycle and a meter showing the share used
  1. Your current plan and what it costs each month.
  2. How much of your monthly allowance you have used, against the full allowance.

Your plan sets a monthly allowance, and every email you send counts toward it, including the ones your app sends. When you reach it:

  • New campaigns and automated flows stop sending until your next billing period, or until you move to a larger plan. A campaign that is already sending carries on.
  • Email from your app, such as receipts and password resets, keeps sending.

If a payment fails, your subscription is overdue while the payment is retried. Email from your app keeps sending, but no new campaign can start, a campaign that is already sending pauses, and automated flows stop sending. Overview shows that payment is overdue. If the subscription ends, nothing sends, from your app or from campaigns, until you subscribe again.

Receipts, tax details and your payment method live in the billing portal, which an owner opens from Billing.

  • Your first send, which covers issuing your first key and choosing a plan.
  • Settings, for the account's settings and your own name and password.
  • API overview, for your developers.