Creates a new user account in the organisation. The ref field is your organisation's unique identifier for the individual and must be unique.
The email field is required unless loginMethod is set to ref.
HTTP Basic authentication using your Tenant ID and API secret.
- Username is the Tenant ID (i.e.
eu-west-2_AbcdEfghI) - Password is the API secret you would have received.
You can also authenticate using OAuth 2.0 client credentials (oauth2 security scheme) instead of Basic auth.
OAuth 2.0 client credentials authentication.
Use the following token endpoints (replace :tenantId with your Tenant ID):
Public API access tokens
- Staging:
https://public.api.learnstaging.link/oauth2/token/:tenantId - Production:
https://public.api.learn.link/oauth2/token/:tenantId - Staging MEA:
https://public.api.meastaging.learn.tech/oauth2/token/:tenantId - Production MEA:
https://public.api.mea.learn.tech/oauth2/token/:tenantId
- Staging:
Webhooks access tokens
- Staging:
https://user.api.learnstaging.link/oauth2/token/:tenantId - Production:
https://user.api.learn.link/oauth2/token/:tenantId - Staging MEA:
https://user.api.meastaging.learn.tech/oauth2/token/:tenantId - Production MEA:
https://user.api.mea.learn.tech/oauth2/token/:tenantId
- Staging:
All access tokens must be sent using the Authorization: Bearer <access_token> header.
Scopes
For API access (non-webhooks), the following scopes are available:
api/all– Full read and write access to the API.api/read– Read-only access to the API.api/write– Write access to the API.
For webhooks, the following scopes are available:
api/webhooks– Access to webhook functionality.api/all– Full read and write access to the API, including webhooks.
Tokens must include appropriate scopes for the endpoints you wish to call.
Create a new user
Creates a new user account with all common fields. The email field is required when loginMethod is 'email' (the default).
"{\n \"ref\": \"UID30084022\",\n \"firstName\": \"Thomas\",\n \"lastName\": \"Jefferson\",\n \"email\": \"user@thrivelearning.com\",\n \"loginMethod\": \"email\",\n \"role\": \"learner\",\n \"jobTitle\": \"Director\",\n \"managerRef\": \"UID0034234555\",\n \"startDate\": \"2021-01-01T09:00:00+00:00\",\n \"timeZone\": \"Europe/London\",\n \"languageCode\": \"en\",\n \"sso\": false,\n \"domain\": \"tenant.learn.link\",\n \"additionalFields\": {\n \"department\": \"Engineering\",\n \"costCentre\": \"CC-001\"\n }\n}\n"The input to create a new user account.
The email field is required unless loginMethod is set to ref.
Your organisation's unique identifier for this individual
The given name of the individual
The family name of the individual
The email address for the user. Required unless loginMethod is 'ref'.
How the user logs in. Defaults to 'email'.
The role assigned to this individual. Defaults to 'learner' if omitted.
The name of this individual's role in your organisation
Your organisation's unique identifier for this individual's line manager
The date this individual started working with your organisation
The date this individual left your organisation
The user's preferred timezone. If not provided the tenant default is used.
The user’s preferred language. If not provided the tenant default is used.
One caveat is that the tenant may only use the languages they have requested.
Whether this account is managed by an Authentication provider or not.
The domain this individual is associated with
Custom field key-value pairs matching your configured custom fields.
OK
A user lifecycle resource returned by the v2 user lifecycle endpoints
The user’s preferred language. If not provided the tenant default is used.
One caveat is that the tenant may only use the languages they have requested.
Whether the account is active or suspended
The date and time the user was created
The date and time the user was last modified
Whether this account is managed by an Authentication provider or not.
The domain this individual is associated with
Custom field key-value pairs for this user
Unsupported Media Type — Content-Type must be application/json
The request could not be processed due to a validation error
Unprocessable Content — validation failed
The request could not be processed due to a validation error
An unexpected error has occurred
When any default error occurs it may be a system failure and persistent errors may require support.
The server is unable to process the request