All Verbs | /vendor_bills_contactlist |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
token | query | string | Yes | |
tokensecret | query | string | Yes | |
query | string | Yes | ||
idvendor | query | int | No | |
idcia | query | int | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
list | form | List<vendorContactInfo> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
result | form | int | No | |
message | form | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
idnumber | form | int | No | |
contact | form | string | No | |
form | string | No | ||
phone | form | string | No | |
fax | form | string | No | |
mobile | form | string | No | |
webaccess | form | string | No | |
idvendor | form | int | No | |
idcia | form | int | 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/vendor_bills_contactlist HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: application/json
Content-Length: length
{"token":"String","tokensecret":"String","email":"String","idvendor":0,"idcia":0}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"list":[{"idnumber":0,"contact":"String","email":"String","phone":"String","fax":"String","mobile":"String","webaccess":"String","idvendor":0,"idcia":0}],"result":0,"message":"String"}