| All Verbs | /post_venuelist |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | Yes | |
| tokensecret | query | string | Yes | |
| query | string | Yes |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| list | form | List<post_venueInfo> | 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 | |
| idcia | form | int | No | |
| idproject | form | string | No | |
| venuename | form | string | No | |
| ledger | form | string | No | |
| eventyn | form | bool | No | |
| cianame | 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_venuelist 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
{
list:
[
{
idnumber: 0,
idcia: 0,
idproject: String,
venuename: String,
ledger: String,
eventyn: False,
cianame: String
}
],
result: 0,
message: String
}