Generate, manage and authenticate users in your team with the API.

Generating new users with the API will add them automatically to your team.

Look up the organizationId of your organization

Before you add new team members to your organization, it's important to find out the organizationId of your organization. You can do this with GET /api/v1/users/me/

*note: for this help article we used a test account which is not in use anymore!

Create a new user for your team

1. create a non-admin team member

To create a new user for your team you need to use the API token of a team admin. Only team admins will be able to add new team members. To add a new user to your team you will have to do a POST request to `/api/v1/users/`

Content: { "firstName": string, "email": string, "organizationId": uuid string }
These 3 fields are required! You can also add "lastName": string but this is optional.

after creating the user it will look like this:

Steve won't have a password so you can add a password field, Steve will have to reset the password or you can send Steve a login token (instructions below).

In the image below, it's shown how to create a password when generating a new user. The password for Lionel will be TESTpassword1.

2. Create a non-admin team member that is managed

If you want a team member that is fully managed by you, you can add additional information to the code. Being managed means that they can't change their personal info of their own profile. Add "isManaged": true

A managed user, like Peter in this example, can't log in with a password reset. He will need a login token.

Create a login token for a user

If you don't want team members to login from the dashboard you can create a login token which logs them in automatically. Do a POST request to `/api/v1/users/{id}/loginTokens/` with an empty body.

If we want to create a login token for Tom from the example above it will look like this:

The URL shown in the return can be used to login without a password. This login URL can be used once within one minute to authenticate a user without requiring any further user input. Simply forward the user to this URL, and they will be authenticated.

If desired, you can append something like &next=/scheduling/ or &next=/meet/{organization}/{meeting-key}/ to the login URL to forward the user to that URL after authenticating.

If a user is already logged in to Vectera when sending them to a login URL, they will first be logged out.

Other API information

Connecting and authenticating with Vectera

Guide: Integrating the booking app

Guide: Generate meeting rooms

API Reference

Did this answer your question?