| POST | /ValidateDetails/ |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| GUID | body | Guid | No | |
| Postcode | body | string | No | |
| Number4 | body | string | No | |
| body | string | No | ||
| EmailConfirm | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| BPID | form | int | No | |
| IsValid | form | bool | No | |
| IsLocked | form | bool | No | |
| AttemptsRemaining | form | int | No | |
| Error | form | 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 /ValidateDetails/ HTTP/1.1
Host: webservices.mbukdatabase.co.uk
Accept: application/json
Content-Type: application/json
Content-Length: length
{"GUID":"00000000000000000000000000000000","Postcode":"String","Number4":"String","Email":"String","EmailConfirm":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"BPID":0,"IsValid":false,"IsLocked":false,"AttemptsRemaining":0,"Error":"String"}