| POST | /Enquiries/Add-Supplier |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SupplierContact | body | string | No | |
| EntityName | body | string | No | |
| PortId | body | int | No | |
| EnquiryId | body | int | No | |
| EnquiryGuid | body | Guid | No | |
| EntityId | body | int | No | |
| AddToAllPorts | body | bool | No | |
| AccountId | body | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Status | form | string | No | |
| EntityContactGuid | form | Guid? | No | |
| Errors | form | List<string> | No |
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
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /Enquiries/Add-Supplier HTTP/1.1
Host: internal.thebunkerbridge.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"SupplierContact":"String","EntityName":"String","PortId":0,"EnquiryId":0,"EnquiryGuid":"00000000000000000000000000000000","EntityId":0,"AddToAllPorts":false,"AccountId":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Status":"String","EntityContactGuid":"00000000000000000000000000000000","Errors":["String"]}