| GET | /lprs/{customerId}/roles/{userId} | Gets users last lpr role used |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserId | path | Guid | Yes | The user id |
| CustomerId | path | Guid | Yes | The customer id |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | Guid | No | |
| UserId | form | Guid | No | |
| CustomerId | form | Guid | No | |
| ComputerId | form | Guid | No | |
| VanId | form | Guid | No | |
| RoleTypeId | form | int | No | |
| BootingOfficerId | form | Guid? | No | |
| EnforcementOfficerId | form | Guid? | No | |
| DateCreated | form | DateTime? | 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 /lprs/{customerId}/roles/{userId} HTTP/1.1
Host: api.paylock.com
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"id":"00000000000000000000000000000000","userId":"00000000000000000000000000000000","customerId":"00000000000000000000000000000000","computerId":"00000000000000000000000000000000","vanId":"00000000000000000000000000000000","roleTypeId":0,"bootingOfficerId":"00000000000000000000000000000000","enforcementOfficerId":"00000000000000000000000000000000","dateCreated":"\/Date(-62135596800000-0000)\/"}