Yunique.Toolkit.API

<back to all web services

MachineList

The following routes are available for this service:
GET/v1/Machine

To override the Content-type in your clients 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/MachineList HTTP/1.1 
Host: plm.gerber.fila.com 
Content-Type: application/xml
Content-Length: length

<MachineList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs" />

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

<MachineListResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs">
  <Machines xmlns:d2p1="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs.POCOs">
    <d2p1:Machine>
      <d2p1:APIEndpoint>String</d2p1:APIEndpoint>
      <d2p1:AppPwd>String</d2p1:AppPwd>
      <d2p1:CDate>0001-01-01T00:00:00</d2p1:CDate>
      <d2p1:CUser>String</d2p1:CUser>
      <d2p1:Description>String</d2p1:Description>
      <d2p1:ID>0</d2p1:ID>
      <d2p1:IPAddress>String</d2p1:IPAddress>
      <d2p1:MDate>0001-01-01T00:00:00</d2p1:MDate>
      <d2p1:MUser>String</d2p1:MUser>
      <d2p1:MachineGUID>String</d2p1:MachineGUID>
      <d2p1:Name>String</d2p1:Name>
      <d2p1:PLMURL>String</d2p1:PLMURL>
      <d2p1:Password>String</d2p1:Password>
      <d2p1:Port>0</d2p1:Port>
      <d2p1:Protocol>String</d2p1:Protocol>
      <d2p1:Status>0</d2p1:Status>
      <d2p1:UserName>String</d2p1:UserName>
    </d2p1:Machine>
  </Machines>
  <status>String</status>
</MachineListResponse>