| All Verbs | /sch_getprojectsByNFCTag |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| token | query | string | No | |
| tokensecret | query | string | No | |
| idcia | query | string | No | |
| idvendor | query | string | No | |
| nfctag | query | 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/sch_getprojectsByNFCTag HTTP/1.1
Host: ssl.buildersaccess.com
Content-Type: text/jsv
Content-Length: length
{
token: String,
tokensecret: String,
idcia: String,
idvendor: String,
nfctag: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
validtoken: String,
tagstatus: String,
errorMsg: String,
found: String,
listProject:
[
{
idnumber: String,
projectname: String,
planname: String,
schdstart: String,
closed: String,
pm1: String,
pm2: String,
pm3: String,
pmshow: String,
status: String,
idcia: String,
city: String,
devname: String,
price: String,
stage: String,
nfctag: String,
ledger: String,
idledger: String,
canEdit: String,
tasktag: String,
cianame: String,
newscheduling: String
}
]
}