| All Verbs | /sch_SaveIntroWalkSign | ||
|---|---|---|---|
| All Verbs | /sch_SaveIntroWalkSignV2022 |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| V2022 | query | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | form | string | No | |
| tokensecret | form | string | No | |
| idintrowalksign | form | string | No | |
| rewalkdate | form | string | No | |
| page1_buyer1sign | form | string | No | |
| page1_buyer2sign | form | string | No | |
| page4_buyer1sign | form | string | No | |
| page4_buyer2sign | form | string | No | |
| page4_pmsign | form | string | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /jsv/reply/sch_SaveIntroWalkSignV2022 HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: text/jsv
Content-Length: length
{
V2022: String,
token: String,
tokensecret: String,
idintrowalksign: String,
rewalkdate: String,
page1_buyer1sign: String,
page1_buyer2sign: String,
page4_buyer1sign: String,
page4_buyer2sign: String,
page4_pmsign: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
validtoken: String,
found: String,
message: String
}