Yunique.Toolkit.API

PackageSchemaList

The following routes are available for this service:
GET	/v1/Package/Schema
GET	/v1/Package/Schema/{PackageID}

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/PackageSchemaList HTTP/1.1 
Host: plm.gerber.fila.com 
Content-Type: application/xml
Content-Length: length

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

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

<PackageSchemaListResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs">
  <Schemas xmlns:d2p1="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs.POCOs">
    <d2p1:PackageSchemaInfo>
      <d2p1:PackageDescription>String</d2p1:PackageDescription>
      <d2p1:PackageID>String</d2p1:PackageID>
      <d2p1:PackageName>String</d2p1:PackageName>
      <d2p1:SchemaDescription>String</d2p1:SchemaDescription>
      <d2p1:SchemaFileName>String</d2p1:SchemaFileName>
      <d2p1:SchemaShortDescription>String</d2p1:SchemaShortDescription>
      <d2p1:SchemaType>String</d2p1:SchemaType>
    </d2p1:PackageSchemaInfo>
  </Schemas>
</PackageSchemaListResponse>