Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.
Knowledge Base
My API_GenAddRecordForm doesn't work unless users sign in first even though I'm supplying a username and password in the URL. Why is this happening?
The following URL is embedded in a third-party application web-page. The QuickBase table 9rtyyrty is not anonymously accessible.
https://www.quickbase.com/db/9rtyyrty?a=API_GenAddRecordForm&username=de...
i) User clicks on the above URL, a new web browser page is opened which displays the Add Record page for the QuickBase table
ii) User populates required fields and clicks the Save button.
iii) At this point the Sign Into QuickBase page is displayed, and after supplying the same username and password embedded in the above URL a new DoAddRecord page is displayed without any of the user entered data.
The problem here is that the username and password supplied in the link to API_GenAddRecordForm only applies to one click. No cookie is passed back to the user's browser to allow them to submit the form. To log them in for the submit operation you should use the API_Authenticate call with an rdr parameter set to the API_GenAddRecordForm URL described above. You should remove the username and password parameters from the URL in the rdr parameter and put them in as parameters to the API_Authenticate function. Like this:
https://www.quickbase.com/db/main?a=api_authenticate&username=demo_reque...
NOTE: QuickBase recommends that you use application tokens when working with API calls (read more about tokens at https://www.quickbase.com/help/app_tokens.html).
- 76931 reads
Rate This
Similar Articles
Browse by Category
Knowledge Base Categories
- Accounts (35)
- Application (45)
- E-Mail (7)
- Fields (41)
- Forms (20)
- Formulas (18)
- General (68)
- Other Product (7)
- Pages (1)
- Product (5)
- Reports (15)
- Roles (4)
- Search (1)
- Tables (6)



Comments
Post new comment