| All Verbs | /bacontract_SaveSignatureFromWeb |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| code | query | string | Yes | |
| buyer1InitialBase64 | query | string | Yes | |
| buyer2InitialBase64 | query | string | Yes | |
| buyer1SignBase64 | query | string | Yes | |
| buyer2SignBase64 | query | string | Yes | |
| kirbytitleSignBase64 | query | string | No | |
| listingBrokerSignBase64 | query | string | No | |
| cooperatingBrokerSignBase64 | query | 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 /json/reply/bacontract_SaveSignatureFromWeb HTTP/1.1
Host: contractssl.buildersaccess.com
Content-Type: application/json
Content-Length: length
{"code":"String","buyer1InitialBase64":"String","buyer2InitialBase64":"String","buyer1SignBase64":"String","buyer2SignBase64":"String","kirbytitleSignBase64":"String","listingBrokerSignBase64":"String","cooperatingBrokerSignBase64":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"message":"String","result":"String"}