Forum Discussion
Hi Brian,
My technical team was able to solve this - the clue was in the image linked below from the JSON listener documentation. These fields need to be included in the payload when you generate the token.
https://helpv2.quickbase.com/hc/article_attachments/10661523058964
Hope that helps - let me know
------------------------------
Jason Gordon
------------------------------
- BrianCrowther2 years agoQrew Trainee
Jason did your team use postman for testing or something else?
------------------------------
Brian Crowther
------------------------------- JasonGordon2 years agoQrew Member
Yes - we used postman but only to be able to develop a proof of concept. I had to update Postman for "JWT Bearer" to be an option in the Authorization tab.
Unfortunately I wasn't signed in & lost the example: for us the turning point was adding those fields from the screenshot I mentioned to the payload section down below.
------------------------------
Jason Gordon
------------------------------- BrianCrowther2 years agoQrew Trainee
At this time, I am just trying to do proof of concept as well. In the example above you added the private key and public key in the respective locations in QuickBase and postman? What tool did you use to generate your key pair?
------------------------------
Brian Crowther
------------------------------