Bridge

EnquiryAddBuyer

Enquiries

The following routes are available for this service:
POST	/Enquiries/Add-Buyer

import datetime
import decimal
from marshmallow.fields import *
from servicestack import *
from typing import *
from dataclasses import dataclass, field
from dataclasses_json import dataclass_json, LetterCase, Undefined, config
from enum import Enum, IntEnum


@dataclass_json(letter_case=LetterCase.CAMEL, undefined=Undefined.EXCLUDE)
@dataclass
class EnquiryAddBuyer:
    enquiry_id: int = 0
    enquiry_guid: Optional[str] = None
    buyer_company: Optional[str] = None
    buyer_email_address: Optional[str] = None
    account_id: int = 0
    entity_id: int = 0


@dataclass_json(letter_case=LetterCase.CAMEL, undefined=Undefined.EXCLUDE)
@dataclass
class EnquiryAddBuyerViewModel:
    status: Optional[str] = None
    entity_contact_guid: Optional[str] = None
    errors: Optional[List[str]] = None

Python EnquiryAddBuyer 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.

POST /Enquiries/Add-Buyer HTTP/1.1 
Host: internal.thebunkerbridge.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"EnquiryId":0,"EnquiryGuid":"00000000000000000000000000000000","BuyerCompany":"String","BuyerEmailAddress":"String","AccountId":0,"EntityId":0}

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

{"Status":"String","EntityContactGuid":"00000000000000000000000000000000","Errors":["String"]}