News & Announcements User Community Developer Community

Welcome to the RingCentral Community

Please note the community is currently under maintenance and is read-only.

Make sure to review our Terms of Use and Community Guidelines.
  Please note the community is currently under maintenance and is read-only.
Home » Developers
Error Account does not exist OAU-222 using Postman to get token
Tags: authentication, get token
Oct 28, 2023 at 12:30pm   •   4 replies  •  0 likes
George Schally

We have set up credentials in the sandbox to get a token, We prefer to test with Postman. We are receiving the error "OAU-222 Account does not exist". We verified the authorization header is correctly set to Basic + base64_encoded( Client ID + ":" + Client Secret ).

We saw another post indicating Authorization and Content-type should be passed in the body of the post, not as headers. When we tried that we got a different error. Any help woudl be greatly appreciated. We downloaded the sample Postman collection, but it seems to be out of date and does not match the JWT Authorization Code Flow as described in the documentation.

4 Answers
answered on Oct 31, 2023 at 12:16pm  

Thank you very much for that Postman collection! I retested and it worked.

answered on Oct 31, 2023 at 11:05am  

Yes, I was agreeing with you, I read it incorrectly. My client ID is:


on Oct 31, 2023 at 11:14am   •  0 likes

Thanks for sharing the app client id. Your app grant type is correctly set for JWT.

So the problem is purely with your Postman /auth call.

Check if you have access to this Postman collection

answered on Oct 30, 2023 at 4:31pm  

Hello Phong, thank you for answering. I can't find the other question at this time, but you were the person who responded as well, stating the grant type and assertion should be placed in the body. I believe the confusion stems from this documentation page, where these items are listed under a heading "Parameter"

After re-testing with these items in the POST body, I receive this error. Do you have any advice? Thanks.

"error" : "invalid_request",

"errors" : [ {

"errorCode" : "OAU-250",

"message" : "Unsupported grant type"

} ],

"error_description" : "Unsupported grant type"


on Oct 30, 2023 at 9:38pm   •  0 likes

Again, you read the document incorrectly. It is under the POST Body section.


What is your app client id?

answered on Oct 29, 2023 at 10:33am  

Where did you find that in the other post indicating that the Authorization and Content type should be passed in the body? It was clearly written in the answer with the code that the grant_type and the assertion must be in the body. The developer who asked that question put them in the query path.

This must be the body params of the POST, not the query params

  1. {
  2. grant_type: 'urn:ietf:params:oauth:grant-type:jwt-bearer',
  3. assertion: JWT,
  4. }


A new Community is coming to RingCentral!

Posts are currently read-only as we transition into our new platform.

We thank you for your patience
during this downtime.

Try Workflow Builder

Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!

Try RingCentral Workflow Builder

Developer Platform
Integrated Apps
App Gallery
Developer support
Games and rewards

Resource center
Product Releases
App Download
RingCentral App login
Admin Portal Login
Contact Sales
© 1999-2024 RingCentral, Inc. All rights reserved. Legal Privacy Notice Site Map Contact Us