Forum Discussion
MishaLeong
5 years agoQrew Member
Hey Mark, sorry for the confusion. I just pasted in the generic code that's in the quickbase documentation for api calls. I have a very long string that I'm using in reality.
------------------------------
Misha Leong
------------------------------
------------------------------
Misha Leong
------------------------------
MarkShnier__You
Qrew Legend
5 years agoWhy not just use an Automation instead of a Webhook? Or is this being called from outside Quick Base?
Any chance there is a leading or trailing space in your usertoken?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Any chance there is a leading or trailing space in your usertoken?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- MishaLeong5 years agoQrew MemberYes, I'm calling this from outside Quick Base. I just checked for leading/trailing spaces that might be a simple solution but no such luck.
I'm a bit surprised that I was getting an "Invalid Application Token" error at all since I thought that having a user token would eliminate that need.
------------------------------
Misha Leong
------------------------------- MarkShnier__You5 years ago
Qrew Legend
I'm not sure what to suggest other than to either disable the need for Application Tokens in the Advanced settings for the app or to provide one in the API call.
I think I was also under the impression that when you use a user token you do not need to supply an application token.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- AustinK5 years agoQrew CommanderThe way you described it is correct based on the help docs, if you use a user token you do not need an app token.
In the real world it seems to be different though. I've run into this several times and now I just provide both the app token and user token by default to prevent it.