Skip to Navigation

Reply to comment

some debugging ideas to try

Hi Wendy --

Sometimes API calls take a couple of tries to get all the details right. Here are some things to check:

The "src" attribute of the first <script> tag is very important. It should contain:

  • the name of the database you want to get the data from (5rh82jcq in the example; you will need to fill in a value from a QuickBase you have access to)
  • the name of the API call you're making (should be correct in the sample, no need to change)
  • a valid authentication ticket returned by API_Authenticate
  • a valid application token (if your application requires them)
  • the identifier for the query (report) you're running (5 in the example)
  • jht=1 (this makes the call return the HTML needed to make the qdbWrite() call work)

Also, it's important to give the user that you use in API_Authenticate access to the table and report that you're embedding. If possible, log in as the user and run the report manually to make sure that all the permissions are correct and the report contains the data you think it will.

If none of these things work and you're still having issues with getting the report to run, please contact QuickBase Support directly to work through this issue:




The content of this field is kept private and will not be shown publicly.
Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.

© 2016 QuickBase, Inc. All Rights Reserved.

Online Database VeriSign Secured Web Based Software TRUSTe Certification Online Database SSAE Audit