| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ErrorNo | form | int | No | |
| Message | form | string | No | |
| Identity | form | long? | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /xml/reply/NcpfAckRequest HTTP/1.1
Host: tstextweb20.np.bluebet.com.au
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<NcpfAckRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions" />
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <NcpfAckResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts"> <ErrorNo>0</ErrorNo> <Identity>0</Identity> <Message>String</Message> </NcpfAckResult>