Sanctions Search API: v2

GetSubUser

Account

The following routes are available for this service:
GET	/subusers/get	Get a sub user

**GetSubUser** Parameters:
Name	Parameter	Data Type	Required	Description
SubUserName	query	string	No	The user name of the sub user
SubUserId	query	Guid?	No	The user id of the sub user

**BaseRequest** Parameters:
Name	Parameter	Data Type	Required	Description
Authentication	header, body	Authentication	Yes	The authentication credentials

**Authentication** Parameters:
Name	Parameter	Data Type	Required	Description
ApiUserId	header, body	string	Yes	The API User ID provided by us when you signed up to use our API. Can be provided in the request body, or as a header parameter (X-Api-User)
ApiUserKey	header, body	string	Yes	The API User Key provided by us when you signed up to use our API. Can be provided in the request body, or as a header parameter (X-Api-Key)
UserId	header, body	string	No	The User ID of the user making the request (e.g. a sub user). This is optional but can be used to associate API requests with a specific user, thereby allowing user permissions to be enforced. Can be provided in the body, or as a header parameter (X-User-Id).

**GetSubUserResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Data	form	GetSubUserData	No	The response data

**GetSubUserData** Parameters:
Name	Parameter	Data Type	Required	Description
SubUser	form	SubUser	No	The sub users

**BaseResponse** Parameters:
Name	Parameter	Data Type	Required	Description
ResponseStatus	form	ResponseStatus	No	The status of the response

**ResponseStatus** Parameters:
Name	Parameter	Data Type	Required
ErrorCode	form	string	No
Message	form	string	No
StackTrace	form	string	No
Errors	form	ArrayOfResponseError	No
Meta	form	Dictionary<string, string>	No

**ResponseError** Parameters:
Name	Parameter	Data Type	Required
ErrorCode	form	string	No
FieldName	form	string	No
Message	form	string	No
Meta	form	Dictionary<string, string>	No

**SubUser** Parameters:
Name	Parameter	Data Type	Required	Description
IsMainUser	form	bool	No	Is this user the main user (i.e. the user who created the account)
UserId	form	Guid	No	The sub user's id (GUID)
UserName	form	string	No	The sub user's UserName (i.e. the sign-in username)
Name	form	string	No	The sub user's name
Email	form	string	No	The sub user's email address
IsAdmin	form	bool	No	Does this sub user have admin privileges, such as managing purchases and sub users
CanResolveSearches	form	bool	No	Can this sub user resolve searches (UpdateSearch) they have access to
CanDeleteSearches	form	bool	No	Can this sub user delete searches (DeleteSearch) they have access to
Permissions	form	ArrayOfUserNames	No	The user names for which searches will be made available to the sub user

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.

GET /subusers/get HTTP/1.1 
Host: api.sanctionssearch.com 
Accept: application/json

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

{"data":{"subUser":{"isMainUser":false,"userName":"String","name":"String","email":"String","isAdmin":false,"canResolveSearches":false,"canDeleteSearches":false,"permissions":["String"]},"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}}