An invite is how someone joins your workspace. You send it to an email address with a role attached; they accept from the email or from their own dashboard, and they appear as a member.
Before you send one
Two conditions have to be true before an invite can even be created, and both catch people out.
They must already have an APIVerve account. An invite to an address with no account behind it is refused on the spot — No APIVerve account found with this email address. The user must have an account to be invited. It is not queued for later. Have them sign up first, on the free plan, and then send the invite to the address they signed up with.
Your own email must be verified. Inviting, cancelling, re-roling and removing all check it. If the invite button returns Please verify your email before inviting team members, that is the whole problem.
Teams themselves need a plan that includes seats — without one, inviting returns a 403 saying
your plan does not include team members:
| Plan | Team members |
|---|---|
| Free | Not included |
| Starter | Not included |
| Pro | 3 |
| Mega | 10 |
Sending one
Teams in the dashboard, then the invite form: an email address and a role, admin or viewer. See roles for what each grants.
The address is lower-cased and trimmed before anything else happens, so capitalisation in what you type does not matter — but the address itself must be exactly the one on their account, because that is how the invite is matched.
Four things the form will refuse, all of them the sensible answer:
- Inviting yourself. Checked against both your address and your account, so neither spelling gets through.
- Someone who is already a member. This user is already a member of your team. Change their role instead.
- A repeat invite inside 24 hours. See below.
- Anything beyond your seat limit. You have reached your team seat limit of N (including pending invites).
A pending invite occupies a seat. Seats count members plus outstanding invites, so an invite nobody answered is a seat nobody is using. You, the owner, do not consume one — the members panel counts you, the seat meter does not. If you are at the limit, cancelling stale invites is the first place to look before upgrading.
Re-sending
Sending to the same person again is a re-send, not a second invite, and it is rate-limited to once every 24 hours. Inside that window you get An invite was recently sent to this email. You can resend in N hours.
A re-send does three things: it refreshes the timestamp, applies whatever role you picked this time, and issues a new token.
Each invite carries a single token, and re-sending replaces it. The link in the earlier email stops working — following it returns Invalid or expired invite token. If someone reports a dead link right after you re-sent, tell them to use the newest email rather than the one they had open.
Because a re-send also updates the role, it is a way to correct a role on an invite that has not been accepted yet — though changing it after they join is quicker, and has no cooldown.
Accepting one
Two routes, and they end in the same place.
From the email. The link carries the token and drops them into the workspace once they are signed in.
From the dashboard. Pending invitations appear at the top of their Teams page with who sent it and what role it grants, alongside Accept and Decline.
Three checks run on acceptance:
- Their email must be verified — Please verify your email before accepting team invites.
- The token must match the current one on the invite, which is what a re-send changes.
- The signed-in account's address must match the address invited. Forwarding an invite to a different address does not transfer it — that returns This invite was sent to a different email address.
An invite that has already been accepted cannot be accepted again; the answer to a member who lost access is a fresh invite, not the old link.
Invites do not expire on a timer. One left unanswered stays valid — and stays on your seat count — until it is accepted or cancelled.
Cancelling and declining
They are the same operation from the two ends of an invite, and both free the seat immediately.
You cancel a pending invite from the Pending invites panel. They won't be able to join with this invite. You can send a new one anytime. The token dies with it.
They decline from their own Teams page.
Neither works once an invite has been accepted — at that point it is a membership, so the actions are remove member and leave team instead. The dashboard says so explicitly rather than silently doing nothing: Cannot cancel an accepted invite. Use remove member instead.
Cancel whenever you invite the wrong address, pick the wrong role and do not want to wait out the re-send cooldown, or find an invite that has gone unanswered long enough to be just a seat you cannot use.
After they join
The new member appears in your team list with their name, email and role, and your workspace appears in their switcher. See workspaces.
From that moment they can see your API keys. That is the intended behaviour — it is what sharing an account means — but it is worth being deliberate about who you invite, because read-only access to the dashboard is still full visibility of the credentials shown in it. See roles.
Removing someone later
Removing a member takes effect immediately: any app or session using their access will stop working immediately, and the seat is freed. They can be invited again afterwards, and the 24-hour cooldown does not apply to someone who is no longer a member.
What removal does not do is invalidate a key they had already copied somewhere. Ending dashboard access and ending a credential are two separate things, and an offboarding that matters does both — see key rotation.
Troubleshooting
"No APIVerve account found with this email address." They have not signed up, or they signed up with a different address. This is by far the most common failure, and it is not something you can fix from your side.
"Please verify your email…" on either side. Verification is required to send, accept, cancel, re-role or remove. Whoever saw the message is the one who needs to verify.
"Invalid or expired invite token." The invite was cancelled, or re-sent — which replaces the token and kills the older link. Have them open the most recent email.
"This invite was sent to a different email address." They are signed in as a different account than the one you invited. Either they switch accounts, or you cancel and invite the address they actually use.
They never got the email. Check the pending invite for a typo in the address, and have them check spam. If it has been under 24 hours you cannot re-send yet — cancelling and inviting again clears the cooldown, since the record goes with it.
They accepted but see nothing. They are still in their own workspace. The switcher in the header is how they get to yours — see workspaces.
Next
Roles covers what to grant. Workspaces covers what a member does once they are in. Teams covers the seat maths that decides how many invites you can have outstanding, and sub-keys are the alternative when the thing needing access is a system rather than a person.