Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

General Information


ServiceAPIMethodData ModelWorkflow
urac

/admin/users/invite

PUTUsers 

Description

  • This API invites users that have an id, username, or email that fits the one sent in the user object in the request body to the tenant or subtenant that has the external key sent in the request headers.
  • The user will have an automatically generated code if the code parameter under the pin object is set to be true.
  • An email with the generated code will be sent to the user.
  • The user will be allowed to trigger pin login if the allowed parameter under the same object is set to be true. If the allowed parameter is set to false, another user with allowed pin login should enable pin login in that specific tenant so users that have pin access can log in by pin.
  • The invited user will have the subtenant that was invited to under allowedTenants array in config object.


Input


Type: application/json
NameSourceMandatoryTypeSpecial FormatDescription
UsersBodyYESObjectincludes user object, groups array, and pin object

NameSourceMandatoryTypeSpecial FormatDescription
groupsBodyNOArrayArray of stringsGroups array
pinBodyNOObjectincludes code and allowed parametersPin Object

NameMandatoryTypeDescription
codeYESBooleanset to True to create a random generated code 
allowedYESBoolean

set to True if this user is allowed to start pin code login

userBodyYESObjectIncludes one of id, username, or emailUser Object

One of the following should exist under the user object:

NameMandatoryTypeSpecial FormatDescription
idYESStringN/AUser ID
usernameYESStringN/AUsername
emailYESStringN/AUser Email


Output


Response

SOAJS has a unified response. Check out this link to understand more the schema of SOAJS response 

Valid Response

Valid Response Sample
{ 
  result: true,
  data: { 
	succeeded: [ { id: '%user_id%' } ],
  	failed: [] 
  }
}
Valid Failed Response Sample
{
  "succeeded": [],
  "failed": [
    {
      "id": "%user_id%",
      "reason": "User has already been invited."
    }
  ]
}

Invalid Response

Error Response Sample
{
    "result":false,
    "errors":{
        "codes":[602],
        "details":[
            {
                "code":602,
                "message":"Model error: + %model_error%"
            }
        ]
    }
}

Response validation

NameMandatoryTypeSpecial FormatDescription
succeededYESArrayArray of ObjectsSucceeded response information

One of the following should exist under the succeeded object:

NameMandatoryTypeSpecial FormatDescription
idYESStringN/AUser ID
usernameYESStringN/AUsername
emailYESStringN/AUser Email
failedYESStringN/AFailed response information

NameMandatoryTypeSpecial FormatDescription
reasonYESStringN/AFailing reason

One of the following should exist also under the succeeded object:

NameMandatoryTypeSpecial FormatDescription
idYESStringN/AUser ID
usernameYESStringN/AUsername
emailYESStringN/AUser Email

Response schema

Follow this link to check out the response JSON Schema


SOAJS Error Codes


Code
Description
400

Business logic required data are missing

520

Unable to find user

602Model error: + %model_error%
  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.