Suspends the user identified by their ref, marking them as inactive in the organisation. An optional endDate can be provided to record when the individual left the organisation.
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.
The user ref
Suspend a user
Suspends the user and optionally records the date they left the organisation.
"{\n \"endDate\": \"2024-06-30T17:00:00.000Z\"\n}\n"The input to suspend a user. All fields are optional.
The date this individual left your organisation
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
Bad Request — path parameter ref is required
The request is invalid
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