All Verbs | /post_getdocument |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
token | query | string | Yes | |
tokensecret | query | string | Yes | |
query | string | Yes | ||
idcia | query | string | No | |
idtenant | query | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
result | form | int | No | |
message | form | string | No | |
list | form | List<documentsInfo> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
id | form | string | No | |
fname | form | string | No | |
revision | form | string | No | |
fsizekb | form | string | No | |
ftype | form | string | No | |
modidate | form | string | No | |
folder | form | string | No | |
xsel | form | string | No | |
creaby | 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_getdocument HTTP/1.1
Host: sdk.lovettcommercial.com
Content-Type: text/jsv
Content-Length: length
{
token: String,
tokensecret: String,
email: String,
idcia: String,
idtenant: String
}
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length { result: 0, message: String, list: [ { id: String, fname: String, revision: String, fsizekb: String, ftype: String, modidate: String, folder: String, xsel: String, creaby: String } ] }