| POST | /ValidateDetails/ |
|---|
package dtos
type ValidateDetailsResponse struct {
Bpid int `json:"bpid,omitempty"`
IsValid bool `json:"isValid,omitempty"`
IsLocked bool `json:"isLocked,omitempty"`
AttemptsRemaining int `json:"attemptsRemaining,omitempty"`
Error *string `json:"error,omitempty"`
}
type ValidateDetailsRequest struct {
Guid string `json:"guid,omitempty"`
Postcode *string `json:"postcode,omitempty"`
Number4 *string `json:"number4,omitempty"`
Email *string `json:"email,omitempty"`
EmailConfirm *string `json:"emailConfirm,omitempty"`
IsSignedUp bool `json:"isSignedUp,omitempty"`
IsPrivacyChecked bool `json:"isPrivacyChecked,omitempty"`
}
Go ValidateDetailsRequest DTOs
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 /ValidateDetails/ HTTP/1.1
Host: webservices.mbukdatabase.co.uk
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<ValidateDetailsRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MBMMFAutoEnrol.ServiceInterface.Services.GetDetails">
<Email>String</Email>
<EmailConfirm>String</EmailConfirm>
<GUID>00000000-0000-0000-0000-000000000000</GUID>
<IsPrivacyChecked>false</IsPrivacyChecked>
<IsSignedUp>false</IsSignedUp>
<Number4>String</Number4>
<Postcode>String</Postcode>
</ValidateDetailsRequest>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <ValidateDetailsResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MBMMFAutoEnrol.ServiceInterface.Services.GetDetails"> <AttemptsRemaining>0</AttemptsRemaining> <BPID>0</BPID> <Error>String</Error> <IsLocked>false</IsLocked> <IsValid>false</IsValid> </ValidateDetailsResponse>