eQuipAPI

CheckforcheckoutAssets

Check for Checkout assets

The following routes are available for this service:
GET	/AssetReservations/CheckforAssets/	Save Transaction in Reserve Assets on checkout

**CheckforcheckoutAssets** Parameters:
Name	Parameter	Data Type	Required	Description
UserID	path	string	Yes	The internal Id of the user
ReservationID	path	string	Yes	Reservation ID of Asset Reservation
AssetList	path	string	Yes	Checkout Assets
IsfromCheckin	path	bool	Yes	Whether call form check in or nots

**CheckinCheckOutWorkflowConfigurationDto** Parameters:
Name	Parameter	Data Type	Required	Description
CheckinWorkflowID	body	string	No	Checkin Workflow ID of Checkin and CheckOut Workflow Configuration
CheckoutWorkflowID	body	string	No	Checkout Workflow ID of Checkin and CheckOut Workflow Configuration

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/CheckforcheckoutAssets HTTP/1.1 
Host: equipstage2.e-isg.com 
Content-Type: application/xml
Content-Length: length

<CheckforcheckoutAssets xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <AssetList>String</AssetList>
  <IsfromCheckin>false</IsfromCheckin>
  <ReservationID>String</ReservationID>
  <UserID>String</UserID>
</CheckforcheckoutAssets>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<CheckinCheckOutWorkflowConfigurationDto xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel.Dto">
  <CheckinWorkflowID>00000000-0000-0000-0000-000000000000</CheckinWorkflowID>
  <CheckoutWorkflowID>00000000-0000-0000-0000-000000000000</CheckoutWorkflowID>
</CheckinCheckOutWorkflowConfigurationDto>