| POST | /customers/{customerId}/officers | Creates a new Officer entry for this Customer. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| CustomerId | path | Guid | Yes | The customer Id. |
| Name | body | string | Yes | The label or name of the new Parking Area. |
| PhoneNumber | body | string | No | The phone number of the new Officer. |
| IsDeleted | body | bool | Yes | Whether the Officer is deleted. |
| CanAuthorizeRelease | body | bool | No | Whether the Officer can authorize release. |
| IsOfficer | body | bool | No | Whether the Officer is a Booting Officer. |
| IsEnforcementOfficer | body | bool | No | Whether the Officer is an Enforcement Officer. |
| RequiredToLoginForBooting | body | bool | No | Whether the Officer is Required to Login for Booting Operations. |
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.
POST /customers/{customerId}/officers HTTP/1.1
Host: api.paylock.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"customerId":"00000000000000000000000000000000","name":"String","phoneNumber":"String","isDeleted":false,"canAuthorizeRelease":false,"isOfficer":false,"isEnforcementOfficer":false,"requiredToLoginForBooting":false}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length "00000000000000000000000000000000"