MBFSPreferences

CustomerPreferencesRequest

The following routes are available for this service:
All Verbs	/CustomerPreferences/

**CustomerPreferencesRequest** Parameters:
Name	Parameter	Data Type	Required
BP_ID	query	string	No
Username	query	string	No
Token	query	string	No
Timestamp	query	string	No

**CustomerPreferencesResponse** Parameters:
Name	Parameter	Data Type	Required	Description
ResponseStatus	form	Response	No
MarketingPreference	form	MarketingPreference	No

**Response** Parameters:
Name	Parameter	Data Type	Required	Description
Code	form	string	No
Message	form	string	No

**MarketingPreference** Parameters:
Name	Parameter	Data Type	Required
OptInMail	form	string	No
OptInTelephone	form	string	No
OptInEmail	form	string	No
OptInSMS	form	string	No
TimeStamp	form	string	No
MMF_Portal_Registered	form	bool	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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /CustomerPreferences/ HTTP/1.1 
Host: webservices.mbukdatabase.co.uk 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"BP_ID":"String","Username":"String","Token":"String","Timestamp":"String"}

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

{"ResponseStatus":{"Code":"String","Message":"String"},"MarketingPreference":{"OptInMail":"String","OptInTelephone":"String","OptInEmail":"String","OptInSMS":"String","TimeStamp":"String","MMF_Portal_Registered":false}}