BootView WebApi

<back to all web services

UpdateCustomerOfficer

The following routes are available for this service:
PUT/customers/{customerId}/officers/{id}Updates an existing Officer entry for this Customer.
UpdateCustomerOfficer Parameters:
NameParameterData TypeRequiredDescription
CustomerIdpathGuidYesThe customer Id.
IdpathGuidYesThe officer Id.
NamebodystringYesThe label or name of the Officer.
PhoneNumberbodystringNoThe phone number of the Officer.
IsDeletedbodyboolYesWhether the Officer is deleted.
CanAuthorizeReleasebodyboolNoWhether the Officer can authorize release.
IsOfficerbodyboolNoWhether the Officer is a Booting Officer.
IsEnforcementOfficerbodyboolNoWhether the Officer is an Enforcement Officer.
RequiredToLoginForBootingbodyboolNoWhether the Officer is Required to Login for Booting Operations

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

HTTP + XML

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

POST /xml/reply/UpdateCustomerOfficer HTTP/1.1 
Host: api.paylock.com 
Content-Type: application/xml
Content-Length: length

<UpdateCustomerOfficer xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BootView.WebApi.ServiceModel">
  <CanAuthorizeRelease>false</CanAuthorizeRelease>
  <CustomerId>00000000-0000-0000-0000-000000000000</CustomerId>
  <Id>00000000-0000-0000-0000-000000000000</Id>
  <IsDeleted>false</IsDeleted>
  <IsEnforcementOfficer>false</IsEnforcementOfficer>
  <IsOfficer>false</IsOfficer>
  <Name>String</Name>
  <PhoneNumber>String</PhoneNumber>
  <RequiredToLoginForBooting>false</RequiredToLoginForBooting>
</UpdateCustomerOfficer>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<guid xmlns="http://schemas.microsoft.com/2003/10/Serialization/">00000000-0000-0000-0000-000000000000</guid>