BokaMera.API.Host

UpdateQvicklyApiSettings

**Requires Authentication**
Requires any of the roles:	bookingsupplier-administrator-write, superadmin

The following routes are available for this service:
PUT	/payment/billmate/apisettings/	Update Qvickly api settings	Update Qvickly api settings for the logged in company

**UpdateQvicklyApiSettings** Parameters:
Name	Parameter	Data Type	Required	Description
CompanyId	body	Guid?	No	The company id, if empty will use the company id for the user you are logged in with.
Id	body	int?	No	The Qvickly id
Secret	body	string	No	The Qvickly secret
ReceiverEmail	body	string	No	The Qvickly receiver email
ReceiverFirstname	body	string	No	The Qvickly receiver firstname
ReceiverLastname	body	string	No	The Qvickly receiver lastname

**QvicklyApiSettingsQueryResponse** Parameters:
Name	Parameter	Data Type	Required	Description
CompanyId	form	Guid	No	The company id
Id	form	int	No	The Qvickly id
Secret	form	string	No	The Qvickly secret
ReceiverEmail	form	string	No	The Qvickly receiver email
ReceiverFirstname	form	string	No	The Qvickly receiver firstname
ReceiverLastname	form	string	No	The Qvickly receiver lastname

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.

PUT /payment/billmate/apisettings/ HTTP/1.1 
Host: testapi.bokamera.se 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"CompanyId":"00000000-0000-0000-0000-000000000000","Id":0,"Secret":"String","ReceiverEmail":"String","ReceiverFirstname":"String","ReceiverLastname":"String"}

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

{"Id":0,"Secret":"String","ReceiverEmail":"String","ReceiverFirstname":"String","ReceiverLastname":"String"}