Forum Discussion
KelechiKelechi
8 years agoQrew Trainee
Thank you very much.. This is what i thought of initially.
- _anomDiebolt_8 years agoQrew EliteTechnically you are not supposed to share a QuickBase ticket among multiple users as it is probably against their terms of service. So even if you had access to the logged in user's ticket, sending it to your server and making API calls to QuickBase from your server might run afoul of the terms of service.
- KelechiKelechi8 years agoQrew TraineeOkay. This means the user will need to login again on the new app. A new user's ticket will be generated.
Now the default ticket hours is 24, What is the maximum ticket hours that can be specified.. I can't seem to find a definitive answer in the docs
Thank you - _anomDiebolt_8 years agoQrew EliteLogging in with API_Authenticate has a default lifetime of 12 hours. You can set &hours but I don't know what the maximum allowed value is as it is not documented and I never test it.
Most of my API work is done client side where the user is already logged in. You never have to call API_Authenticate in this scenario. The ticket will be sent on every call to quickbase.com automatically as a HTTP Only Cookie.
In you scenario you would have to call API_Authenticate from your server to QuickBase and set the &hours parameter appropriately.