Pera ServiceStack

<back to all web services

ContactOrganizationTypeRequest

The following routes are available for this service:
GET,OPTIONS/v1/ContactOrganizationType

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

<ContactOrganizationTypeRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/PeraServiceStackLibrary" />
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<ContactOrganizationResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/PeraServiceStackLibrary">
  <Organization xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
    <d2p1:string>String</d2p1:string>
  </Organization>
  <OrganizationType>
    <OrganizationType>
      <DisplayFor>String</DisplayFor>
      <OrganizationTypeId>0</OrganizationTypeId>
      <OrganizationTypeName>String</OrganizationTypeName>
    </OrganizationType>
  </OrganizationType>
  <ResponseStatus xmlns:d2p1="http://schemas.servicestack.net/types">
    <d2p1:ErrorCode>String</d2p1:ErrorCode>
    <d2p1:Message>String</d2p1:Message>
    <d2p1:StackTrace>String</d2p1:StackTrace>
    <d2p1:Errors>
      <d2p1:ResponseError>
        <d2p1:ErrorCode>String</d2p1:ErrorCode>
        <d2p1:FieldName>String</d2p1:FieldName>
        <d2p1:Message>String</d2p1:Message>
      </d2p1:ResponseError>
    </d2p1:Errors>
  </ResponseStatus>
</ContactOrganizationResponse>