BootView WebApi

<back to all web services

UpdateCustomerReturnLocation

The following routes are available for this service:
PUT/customers/{customerId}/returnlocations/{id}Updates an existing return location. Fails if the return location doesn't exist.
UpdateCustomerReturnLocation Parameters:
NameParameterData TypeRequiredDescription
CustomerIdpathGuidYesThe customer Id.
IdpathGuidYesThe return location Id.
NamebodystringYesThe label or name of the return location.
AddressbodystringNoThe complete address of the return location.
PhoneNumberbodystringNoThe phone number of the return location.
PhoneNumber2bodystringNoThe alternate phone number of the return location.
ContactNamebodystringNoThe contact name of the return location.
IsDeletedbodyboolYesWhether the return location is deleted. Default is false when not supplied.
IsMappablebodyboolYesWhether the new return location is mappable.
MapStreetbodystringNoThe Map Street Address of the new return location.
MapCitybodystringNoThe Map City of the new return location.
MapStatebodystringNoThe Map State of the new return location.
MapRegionbodyintNoThe Map Region of the new return location.
MapPostalCodebodystringNoThe Map Postal Code of the new return location.
CrossStreetbodystringNoThe location Cross Street description
LatitudebodydecimalNoLatitude
LongitudebodydecimalNoLongitude
AdditionalInformationbodystringNoAdditional information to be shown by MyBootInfo
IsDefaultbodyboolYesWhether the new return location is the default.
IsMotoristReturnLocationbodyboolNoWhether the new return location is accessible to motorists
ReturnLocationTimingsbodyList<CustomerReturnLocationTiming>NoAn array of objects representing the operating hours of the returnLocation.
CapacitybodyintNoThe maximum number of boots that can be stored at this location.
ThresholdbodyintNoThe threshold of the location to be used for alerts and reports
BootCountbodyintNoHow many boots are currently at this location.
CustomerReturnLocationTiming Parameters:
NameParameterData TypeRequiredDescription
ReturnLocationIdformGuidNo
DayCodeformintNo
FromformstringNo
ToformstringNo

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/UpdateCustomerReturnLocation HTTP/1.1 
Host: api.paylock.com 
Content-Type: application/xml
Content-Length: length

<UpdateCustomerReturnLocation xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BootView.WebApi.ServiceModel">
  <AdditionalInformation>String</AdditionalInformation>
  <Address>String</Address>
  <BootCount>0</BootCount>
  <Capacity>0</Capacity>
  <ContactName>String</ContactName>
  <CrossStreet>String</CrossStreet>
  <CustomerId>00000000-0000-0000-0000-000000000000</CustomerId>
  <Id>00000000-0000-0000-0000-000000000000</Id>
  <IsDefault>false</IsDefault>
  <IsDeleted>false</IsDeleted>
  <IsMappable>false</IsMappable>
  <IsMotoristReturnLocation>false</IsMotoristReturnLocation>
  <Latitude>0</Latitude>
  <Longitude>0</Longitude>
  <MapCity>String</MapCity>
  <MapPostalCode>String</MapPostalCode>
  <MapRegion>0</MapRegion>
  <MapState>String</MapState>
  <MapStreet>String</MapStreet>
  <Name>String</Name>
  <PhoneNumber>String</PhoneNumber>
  <PhoneNumber2>String</PhoneNumber2>
  <ReturnLocationTimings>
    <CustomerReturnLocationTiming>
      <DayCode>0</DayCode>
      <From>String</From>
      <ReturnLocationId>00000000-0000-0000-0000-000000000000</ReturnLocationId>
      <To>String</To>
    </CustomerReturnLocationTiming>
  </ReturnLocationTimings>
  <Threshold>0</Threshold>
</UpdateCustomerReturnLocation>
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>