Pera ServiceStack

<back to all web services

CRM_ContactDeleteRequest

The following routes are available for this service:
DELETE,OPTIONS/v1/CRM_Contact/{CompanyId}/{AgentId}/{PeraContactId}

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

<CRM_ContactDeleteRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/PeraServiceStackLibrary">
  <AgentId>0</AgentId>
  <CompanyId>0</CompanyId>
  <PeraContactId>0</PeraContactId>
</CRM_ContactDeleteRequest>

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

<CRM_ContactDeleteResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/PeraServiceStackLibrary">
  <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>
  <Success>false</Success>
</CRM_ContactDeleteResponse>