Bridge

EnquiryChatDetails

Chats

The following routes are available for this service:
GET	/Chats/Details

using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using Bridge.Private.Api.DTO;
using Bridge.Core.ViewModels;

namespace Bridge.Core.ViewModels
{
    public partial class ChatDetailsViewModel
    {
        public virtual int VesselId { get; set; }
        public virtual int EntityContactId { get; set; }
        public virtual Guid EntityContactGuid { get; set; }
        public virtual Guid EntityContactImageGuid { get; set; }
        public virtual string EntityContactFirstName { get; set; }
        public virtual string EntityContactLastName { get; set; }
        public virtual Guid ChatGuid { get; set; }
        public virtual string ChattingWithEntityContactFirstName { get; set; }
        public virtual string ChattingWithEntityContactLastName { get; set; }
        public virtual string ChattingWithEntityContactJobTitle { get; set; }
        public virtual string ChattingWithEntityName { get; set; }
        public virtual bool SingleChat { get; set; }
        public virtual int ChattingWithEntityContactId { get; set; }
        public virtual Guid ChattingWithEntityContactGuid { get; set; }
        public virtual string ChattingWithEntityContactRole { get; set; }
        public virtual int ChattingWithEntityId { get; set; }
        public virtual string ChattingWithEntityContactEmailAddress { get; set; }
        public virtual bool NominateSellerAlreadyUsed { get; set; }
        public virtual string ActiveChatAuthorIds { get; set; }
        public virtual string BannerText { get; set; }
        public virtual Guid ChattingWithEntityContactImageGuid { get; set; }
    }

}

namespace Bridge.Private.Api.DTO
{
    public partial class EnquiryChatDetails
    {
        public virtual Guid Id { get; set; }
        public virtual bool SingleChat { get; set; }
    }

}

C# EnquiryChatDetails DTOs

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

GET /Chats/Details HTTP/1.1 
Host: internal.thebunkerbridge.com 
Accept: application/json

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

{"VesselId":0,"EntityContactId":0,"EntityContactGuid":"00000000000000000000000000000000","EntityContactImageGuid":"00000000000000000000000000000000","EntityContactFirstName":"String","EntityContactLastName":"String","ChatGuid":"00000000000000000000000000000000","ChattingWithEntityContactFirstName":"String","ChattingWithEntityContactLastName":"String","ChattingWithEntityContactJobTitle":"String","ChattingWithEntityName":"String","SingleChat":false,"ChattingWithEntityContactId":0,"ChattingWithEntityContactGuid":"00000000000000000000000000000000","ChattingWithEntityContactRole":"String","ChattingWithEntityId":0,"ChattingWithEntityContactEmailAddress":"String","NominateSellerAlreadyUsed":false,"ActiveChatAuthorIds":"String","BannerText":"String","ChattingWithEntityContactImageGuid":"00000000000000000000000000000000"}