API_GenResultsTable and problem with usertoken – Bad Ticket

  • 0
  • 1
  • Question
  • Updated 1 year ago
  • In Progress
I’m using API_GenResultsTable to present Quickbase data on my web site. I’m using a usertoken and apptoken for authentication. I’ve been getting the following error return on occasion. 4 Bad ticket Your ticket has expired. By default, tickets expire after 12 hours of use. One-time tickets expire after 5 minutes. Please log in again. I’m thinking that the API call is picking up an expired cookie ticket from a previous logon to my Quickbase site. Is there a way that I can force the API call to ignore local cookies and use the usertoken. This seems like a bug and is causing issues for my users.
Photo of Mark

Mark

  • 30 Points

Posted 1 year ago

  • 0
  • 1
Photo of John Thomas

John Thomas

  • 1,062 Points 1k badge 2x thumb

usertoken: yes, one of:

  • ticket
  • username/password
  • user token
apptoken: yes, if the application requires application tokens

I hope this will solve your issue, if any clarifications. Happy to help you :) 
Photo of Matthew Neil

Matthew Neil

  • 31,438 Points 20k badge 2x thumb
User tokens should be superior to any local cookies, and the token might not even be needed.

I'd suspect that it has to do with how you are displaying the data within your website.

How are you going about that?  iFrame with a straight URL? 
Photo of Mark

Mark

  • 30 Points
Thanks for you input.

<script type="text/javascript" src="https://mydomain.quickbase.com/db/bmpyuqy99?a=API_GenResultsTable&qid=99&jht=1&usertoken...; </script>