| All Verbs | /sch_SaveIntroWalkSign |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| idintrowalksign | query | string | No | |
| rewalkdate | query | string | No | |
| page1_buyer1sign | query | string | No | |
| page1_buyer2sign | query | string | No | |
| page4_buyer1sign | query | string | No | |
| page4_buyer2sign | query | string | No | |
| page4_pmsign | 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/sch_SaveIntroWalkSign HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: application/json
Content-Length: length
{"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: application/json
Content-Length: length
{"validtoken":"String","found":"String","message":"String"}