For ours I believe the method on QB side was "post".
The terminal commands I used on my mac to generate keys are:
- openssl genrsa -out private.pem 2048
- openssl rsa -in private.pem -pubout > public.pem
I used jwt.io to validate before sending to quickbase - if that side doesn't recognize the token as valid quickbase won't either.
------------------------------
Jason Gordon
------------------------------
Original Message:
Sent: 03-27-2023 14:30
From: Brian Crowther
Subject: Incoming JSON or Incoming Request JWT Token

------------------------------
Brian Crowther
Original Message:
Sent: 03-27-2023 14:27
From: Brian Crowther
Subject: Incoming JSON or Incoming Request JWT Token

------------------------------
Brian Crowther
Original Message:
Sent: 03-27-2023 14:26
From: Brian Crowther
Subject: Incoming JSON or Incoming Request JWT Token
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
Original Message:
Sent: 03-27-2023 14:17
From: Jason Gordon
Subject: Incoming JSON or Incoming Request JWT Token
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
Original Message:
Sent: 03-27-2023 13:51
From: Brian Crowther
Subject: Incoming JSON or Incoming Request JWT Token
Jason did your team use postman for testing or something else?
------------------------------
Brian Crowther
Original Message:
Sent: 03-23-2023 14:00
From: Jason Gordon
Subject: Incoming JSON or Incoming Request JWT Token
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
Original Message:
Sent: 03-16-2023 18:08
From: Brian Crowther
Subject: Incoming JSON or Incoming Request JWT Token
I am using postman to test API connections to Quickbase Post, create new record. I can post and create a new record with fields populated correctly using basic or no authentication. As soon as I try to use a JWT Token, I get an "error": "Unauthorized" in postman and no action on the Quickbase side, not even an error that an attempt was made. Does anyone have a good test setup that I can work with that was successful using postman or another API testing platform?
Using RS256 Public and Privet Key.
------------------------------
Brian Crowther
------------------------------