{
"opencollection": "1.0.0",
"info": {
"name": "emnify REST subpackage_applicationTokens subpackage_passwordManagementAndActivation API",
"version": "1.0.0"
},
"request": {
"auth": {
"type": "bearer",
"token": "{{bearerToken}}"
}
},
"items": [
{
"info": {
"name": "subpackage_passwordManagementAndActivation",
"type": "folder"
},
"items": [
{
"info": {
"name": "Activate user",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://cdn.emnify.net/api/v1/user/activation",
"body": {
"type": "json",
"data": "{}"
}
},
"docs": "Activates the user account and sets a password.\nThe activation key is sent via email.\n\n\n This is a public (unauthenticated) service which ignores auth tokens.\n\n"
},
{
"info": {
"name": "Resend user activation email",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://cdn.emnify.net/api/v1/user/activation_resend",
"body": {
"type": "json",
"data": "{}"
}
},
"docs": "Re-sends activation mail to the user.\n\nAs this endpoint is open to the public (no authentication token necessary), it requires instead the google reCAPTCHA token to ensure that no robot is performing the request.\nMoreover, there's a time limit on how often a given user may be issued with a new activation mail.\n\n\n According to the [reCAPTCHA documentation](https://developers.google.com/recaptcha/docs/display) a \"Site Key\" is necessary.\n If you want to implement this feature in your client"
},
{
"info": {
"name": "Change password",
"type": "http"
},
"http": {
"method": "PATCH",
"url": "https://cdn.emnify.net/api/v1/user/password",
"headers": [
{
"name": "Authorization",
"value": ""
}
],
"body": {
"type": "json",
"data": "{}"
}
},
"docs": "Changes the password for the currently authenticated user.\n\n\n The client application should invalidate the authentication token.\n\n"
},
{
"info": {
"name": "Invite a user",
"type": "http"
},
"http": {
"method": "POST",
"url": "https://cdn.emnify.net/api/v2/user/invitation",
"headers": [
{
"name": "Authorization",
"value": ""
}
],
"body": {
"type": "json",
"data": "{}"
}
},
"docs": "Invite a user to a Workspace by specifying username and the roles that the user will have in the organization.\nThis user is created and a `User invited` event is sent.\nThere is no additional action such as an email sent.\n\nThe following fields may be provided:\n- `username` (String) - Email of the invited user\n- `name` (String) - Name of the invited user\n- `organisation` (Object) - Defaults to the default Workspace of the requesting user\n- `roles` (Array) - Assigns the **Administrator** role by de"
}
]
}
],
"bundled": true
}