| GET | /RS/CurUser |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| curUser | form | CurUser | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserId | form | int | No | |
| UnId | form | int | No | |
| TaxCode | form | string | No | |
| OrgName | form | string | No | |
| Username | form | string | No | |
| Password | 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
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /RS/CurUser HTTP/1.1 Host: 10.10.0.107 Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}},"curUser":{"UserId":0,"UnId":0,"TaxCode":"String","OrgName":"String","Username":"String","Password":"String"}}