@vRaj1
In the documentation that you linked to, you will find the definitions for the request. I'll let you decide which ones are important for your institution.
Probably the most commonly missed idea is that the properties like user[name] need to be nested in JSON.
This may not hit all of the content that you need to set, but it should look something like this:
{
"user" : {
"name" : "John Smith",
"skip_registration" : true
},
"pseudonym" : {
"unique_id" : "jsmith",
"password" : "changeMe",
"sis_user_id" : 1234
},
"communication_channel" : {
"type" : "email",
"address" : "jsmith@example.com",
"skip_confirmation" : false
}
}
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.