Forum Discussion

BrettBrett's avatar
BrettBrett
Qrew Trainee
8 years ago

Recent Issues QB API through Java HttpClient

We've been experiencing some weird issues lately related to the Quickbase API and accessing it via a java httpClient.  We've used the API for ~7 years now and recently, our requests have stopped working for some reason.  They seem to be working after a restart for approximately 8 hours and then just stop working afterward, no exceptions, no indication of the cause. 

Has anyone experienced anything similar?  Anyone have any solutions?

For reference, we make a GET request to the API_Authenticate and then utilizing the API_DoQuery api to query tables in the Quickbase.  We do this for every request so I don't think it would be a session timeout issue unless something has changed on the QB side.

Thanks in advance,
Brett
  • Might you be hitting a quota on the number of API calls you are making per day? Hard to debug without access to server logs. Unless someone else has had the same problem and found a resolution your probably have to go through support. If they get you a resolution I would like to know learn what the issue was.
  • Hi Brett,

    Dan is correct that your best bet for a first step is to submit a ticket to our Support Team so that they can help you to look into those API calls and try to identify where in the process they are failing. They can help you to check for errors that might not be getting caught on your end. Quick Base Support can be accessed by clicking the Help Question Mark at the top right hand corner of the screen when signed into an application or from the My Apps page. Once the help page opens up you would select manage support cases.



    Thank you very much for your time today Brett.
  • Thanks, I reached out to support and they told me to reach out here...
  • When you run these calls Brett what error messages are you getting back when they fail?
  • None, unfortunately it simply isn't returning any data.  It could be a lack of logging on our side but it's hard to tell.  I'm starting to thing that the API_Authenticate doesn't refresh the ticket each time it's called which is allowing our httpClient's session to expire and simply denying the requests afterward.  It would have been a change on the QB side as we've always done it this way but can't find any details. 
    • _anomDiebolt_'s avatar
      _anomDiebolt_
      Qrew Elite
      You need to log the XML response returned by API_Authenticate. It will look like this:
      <qdbapi>
        <action>api_authenticate</action>
        <errcode>0</errcode>
        <errtext>No error</errtext>
        <ticket>2_beeinrxmv_dpvx_b_crf8ttndjwyf9bui94rhciirqcs</ticket>
        <userid>112245.efy7</userid>
      </qdbapi>
      I don't know the range of errors off the top of my head because it is hard to get the credentials wrong and I have never had a problem.

      Something changed either on your end or theirs.

      https://help.quickbase.com/api-guide/index.html#authenticate.html
    • _anomDiebolt_'s avatar
      _anomDiebolt_
      Qrew Elite
      BTW, it would be extremely unlikely to me that QuickBase would not return a new ticket each and every time you call API_Authenticate.
  • I would agree with Dan to my understanding API_Authenticate is set up to return a new ticket for each call. What time interval do you set your API_Authenticate tickets to?