Yunique.API.REST

<back to all web services

LookupType2TypeCUD

The following routes are available for this service:
POST,OPTIONS/v3/Lookup/Type2Type/{ParentLookupID}
DELETE,OPTIONS/v3/Lookup/Type2Type/{ParentLookupID}

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/LookupType2TypeCUD HTTP/1.1 
Host: ncsu.yuniquecloud.com 
Content-Type: application/xml
Content-Length: length

<LookupType2TypeCUD xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs">
  <LookupType2Types xmlns:d2p1="http://schemas.datacontract.org/2004/07/Yunique.API.Rest.DTOs.POCOs">
    <d2p1:LookupType2TypeItem>
      <d2p1:Active>0</d2p1:Active>
      <d2p1:CDate>0001-01-01T00:00:00</d2p1:CDate>
      <d2p1:CUser>String</d2p1:CUser>
      <d2p1:ItemKey>String</d2p1:ItemKey>
      <d2p1:ItemSort>0</d2p1:ItemSort>
      <d2p1:ItemValue>String</d2p1:ItemValue>
      <d2p1:LookupID>00000000-0000-0000-0000-000000000000</d2p1:LookupID>
      <d2p1:LookupTypeActive>0</d2p1:LookupTypeActive>
      <d2p1:LookupTypeID>00000000-0000-0000-0000-000000000000</d2p1:LookupTypeID>
      <d2p1:LookupTypeName>String</d2p1:LookupTypeName>
      <d2p1:MDate>0001-01-01T00:00:00</d2p1:MDate>
      <d2p1:MUser>String</d2p1:MUser>
      <d2p1:ParentLookupID>00000000-0000-0000-0000-000000000000</d2p1:ParentLookupID>
    </d2p1:LookupType2TypeItem>
  </LookupType2Types>
  <ParentLookupID>String</ParentLookupID>
</LookupType2TypeCUD>

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

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