NectaVendorsApi

SaveVendorUser

**Requires Authentication**
Required permission:	create_vu

The following routes are available for this service:
PUT	/admin/vendorUser/save

**SaveVendorUser** Parameters:
Name	Parameter	Data Type	Required	Description
LoginUrl	body	string	No
VendorUser	body	VendorUserDto	No

**VendorUserDto** Parameters:
Name	Parameter	Data Type	Required	Description
UserId	form	int	No
Id	form	int	No	The only use case is validation.
UserName	form	string	No
Role	form	Role	No
AuthMethod	form	AuthMethod	No
Deactivated	form	bool	No
HasDeactivatedStateChanged	form	bool	No
Delete	form	bool	No
UserPermissions	form	List<UserPermissionDto>	No

**UserPermissionDto** Parameters:
Name	Parameter	Data Type	Required
UserId	form	int	No
UserPermissionTypeId	form	int	No
Active	form	bool	No
RoleId	form	int	No

**ResponseSaveVendorUser** Parameters:
Name	Parameter	Data Type	Required	Description
VendorUser	form	VendorUserDto	No
ErrorMsg	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

PUT /admin/vendorUser/save HTTP/1.1 
Host: vendor-api.digisupply.klueh.de 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"LoginUrl":"String","VendorUser":{"UserId":0,"Id":0,"UserName":"String","Role":1,"AuthMethod":0,"Deactivated":false,"HasDeactivatedStateChanged":false,"Delete":false,"UserPermissions":[{"UserId":0,"UserPermissionTypeId":0,"Active":false,"RoleId":0}]}}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"VendorUser":{"UserId":0,"Id":0,"UserName":"String","Role":1,"AuthMethod":0,"Deactivated":false,"HasDeactivatedStateChanged":false,"Delete":false,"UserPermissions":[{"UserId":0,"UserPermissionTypeId":0,"Active":false,"RoleId":0}]},"ErrorMsg":"String"}