> For the complete documentation index, see [llms.txt](https://apis.rightrev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apis.rightrev.com/getting-started/using-implicit-or-password-flow.md).
# Using Implicit or Password Flow
## **To Authenticate and Execute RightRev API using Implicit or Password Flow**
* Go to top of the Swagger. In the **Servers** drop-down select the OAuth server URL, provide the **tenantId** and **Environment** and then click on **Authorize** button as shown in the screenshot below.
* Generate token using one of the flows
### For Implicit Flow
1. Provide the **client\_id** value as Swagger and click **Authorize** button as shown in the screenshot below\
2. Page will open on the browser to authenticate, enter credentials and login.
3. Once the token is validated, you will be viewing the below screenshot and then click on **Close** button
### For Password Flow
1. Enter provided **client\_id**, **client\_secret**, **username** and **password**
2. Click on **Authorize** button
3. Once the token is validated, you will be viewing the below screenshot and then click on **Close** button
4. Click on **Close** button
5. Once you have generated the token now change the URL in the **Servers** drop-down to point to the API server. Now provide the same **tenantId** and **Environment** for which you have generated a token
#### Once you are done with the above steps, click on any one of the APIs and try it out.
{% hint style="info" %}
Token time interval is 5 minutes
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://apis.rightrev.com/getting-started/using-implicit-or-password-flow.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
