Bombshell Chat

<back to all web services

PutConversation

The following routes are available for this service:
PUT, OPTIONS/v1/Conversation

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/PutConversation HTTP/1.1 
Host: chatapi.bombshelltechnologies.com 
Content-Type: application/xml
Content-Length: length

<PutConversation xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BombshellChatServiceStack.Routes">
  <ClientAgentId>0</ClientAgentId>
  <ClientId>00000000-0000-0000-0000-000000000000</ClientId>
  <ContactId>00000000-0000-0000-0000-000000000000</ContactId>
  <ConversationId>00000000-0000-0000-0000-000000000000</ConversationId>
</PutConversation>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<PutConversationResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/BombshellChatServiceStack.Routes">
  <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>
  <Result>false</Result>
</PutConversationResponse>