| All Verbs | /post_pm_vendorList |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| query | string | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| result | form | int | No | |
| message | form | string | No | |
| list | form | List<tenantVendor> | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| idpropertywork | form | string | No | |
| workname | form | string | No | |
| idvendor | form | string | No | |
| name | form | string | No | |
| form | string | No | ||
| address | form | string | No | |
| phone1 | 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/post_pm_vendorList HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: text/jsv
Content-Length: length
{
token: String,
tokensecret: String,
email: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
result: 0,
message: String,
list:
[
{
idpropertywork: String,
workname: String,
idvendor: String,
name: String,
email: String,
address: String,
phone1: String
}
]
}