| All Verbs | /CreateUserSetRoleScope |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| APIKEY | query | string | No | |
| UserIDInternal | query | string | No | |
| user_name | query | string | No | |
| email_address | query | string | No | |
| phone_number | query | string | No | |
| equip_role | query | string | No | |
| equip_site | query | string | No | |
| equip_locationcategories | query | string | No | |
| equip_assetcategories | query | string | No | |
| equip_peoplecategories | query | string | No | |
| equip_department | query | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /xml/oneway/CreateUserSetRoleScope HTTP/1.1
Host: equipstage3.e-isg.com
Content-Type: application/xml
Content-Length: length
<CreateUserSetRoleScope xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<APIKEY>String</APIKEY>
<UserIDInternal>String</UserIDInternal>
<email_address>String</email_address>
<equip_assetcategories>String</equip_assetcategories>
<equip_department>String</equip_department>
<equip_locationcategories>String</equip_locationcategories>
<equip_peoplecategories>String</equip_peoplecategories>
<equip_role>String</equip_role>
<equip_site>String</equip_site>
<phone_number>String</phone_number>
<user_name>String</user_name>
</CreateUserSetRoleScope>