Forum Discussion

BrianCafferelli's avatar
BrianCafferelli
Quickbase Staff
6 years ago

The next generation of the Quickbase API

The next generation of the Quickbase API When we first released our library of Quickbase APIs, it was a historic moment. We were far in front of the rest of the market in making it easy for people...
hhersch's avatar
hhersch
Quickbase Staff
6 years ago

@Nick Wade They are Quick Base pages or hosted in a CDN for example and pulled into a browser.​ I'll add some color. When we talk about CORS, there are two categories:

  1. A JavaScript page in realm1.quickbase.com calling realm2.quickbase.com. We don't allow this today and won't in the future.
  2. A page "served" completely outside of Quick Base (like www.mydomain.com) into someone's browser.
For #2, we will allow CORS from that other domain to the new api endpoint. However, it is important to note that the new API will not allow you to piggyback on the user's current QB session. Since you also should never hardcode a usertoken in JavaScript, the data would either need to be available EOTI or using an intermediary solution hosted on a server.
​