Application Variable

We're getting closer with this, but the variable is a token for us and would need to change at the exact time another site is changing that variable.  It works much like a handshake.

I assume the other site is issuing some type of token that is valid for a certain amount of time and you need to port that token over to QuickBase so you can make URL calls to that external service. Is this correct?

By what mechanism does QuickBase become aware that the token issued from the other site has been issued or changed? Does the other site post to QuickBase or does Quick Base pull the token from the other site?

Yes!  The token changes with time stamps.  The other site looks at the token in QB and then checks its own database for the same token (also the same formula).

>The other site looks at the token in QB and then checks its own database for the same token (also the same formula).

This describes how the token is validated and used one it is know to exist (valid or not). That isn't what I asked. How does QuickBase become aware of a newly issued token or a changed token? Is the token pushed or pulled from the other site?

Pulled.

So you have to arrange for JavaScript in a code page to make a request to the server issuing the token. When the response arrives you parse out the token and save it in a QuickBase application variable using API_SetDBvar. Once a fresh token is saved in an application variable your URL formulas in all the tables can reference it in that various URLs that access the external service.

I don't know what external service you are using so I can't provide any additional advice. There will certainly be more steps to get the token issued as you probably have to log into that service before even requesting for a token.

Interesting....  so, every time we make a call to QB, FIRST set the DBVar and THEN check the token with the call...  Definitely, doable...  Then I am only changing the token formula on one issuing server.  Thank you so much for your help!  

I think you understand what I said but I don't understand your summary:

 "so, every time we make a call to QB, FIRST set the DBVar and THEN check the token with the call."

You seem to be using "we" as representing the external server.

The context above seems to be reversed from what I said. To be explicit: Script in a QuickBase code page makes a request to the external server for a token and caches  the token in a user defined variable which formulas URLs can then use to make subsequent resource requests to the external for the period of time the token is valid.

You are correct....  I misread your response.  I thought it was on an external server.  That makes even more sense...