RESTful API Header
Hello, using RESTful API a temporary token is returned and logged with console.log(xmlHttp.responseText); . Does anyone know how to then pass that temporary token to the 'Authorization': '{Authoriz...
Forum Discussion
I've been following this thread and bashing my face against this brick wall all day. I've been seeing something similar to you Austin.
So, just for kicks, I changed
xmlHttp1.open('GET', 'https://api.quickbase.com/v1/auth/temporary/[MY TABLEID]', true false);
This made it run in synchronous mode, and now my query went straight through like it was supposed to when I set the query's header to 'Authorization': 'QB-TEMP-TOKEN ' + ticket.temporaryAuthorization,
------------------------------
Brad Lemke
------------------------------
So, just for kicks, I changed
xmlHttp1.open('GET', 'https://api.quickbase.com/v1/auth/temporary/[MY TABLEID]', true false);
This made it run in synchronous mode, and now my query went straight through like it was supposed to when I set the query's header to 'Authorization': 'QB-TEMP-TOKEN ' + ticket.temporaryAuthorization,
------------------------------
Brad Lemke
------------------------------
This is my experience in general when trying to slap together a bunch of code examples, it is so hard to debug. This was driving me crazy too because it seemed like it should be working. That's why I had to actually try testing it today to see what was going on.
I should have looked at the xmlHttp command closer. Switching that to false does make that into a synchronous call which should make it all work. From everything I see online this is technically bad practice because it can cause a wait for the user but in this case I don't think it would really matter. I bet it never even causes a problem in this case, there isn;t anything major going on and I don't expect Quickbase to not answer an api call.
Thanks for posting that Brad.
I should have looked at the xmlHttp command closer. Switching that to false does make that into a synchronous call which should make it all work. From everything I see online this is technically bad practice because it can cause a wait for the user but in this case I don't think it would really matter. I bet it never even causes a problem in this case, there isn;t anything major going on and I don't expect Quickbase to not answer an api call.
Thanks for posting that Brad.