ContributionsMost RecentMost LikesSolutionsRe: Incoming JSON or Incoming Request JWT Token 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 ------------------------------ Re: 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 ------------------------------ Re: 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 ------------------------------ Re: Incoming JSON or Incoming Request JWT Token Same here, tried RS256 and RS512. ------------------------------ Jason Gordon ------------------------------