> 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/welcome.md). # Welcome! ## RightRev API's RightRev seamlessly integrates with your sales and revenue accounting processes, offering a united platform for sales operations and revenue reporting across all products and services. RightRev provides a set of APIs which are used in its Revenue Automation process and helps you to perform actions that you do with our web client. RightRev API's are REST and GraphQL based, and Uses OAuth2 for authorization, authentication and returns responses in JSON. Every resource is exposed as a URL. The URL of each resource can be obtained by accessing the API Root Endpoint. All URLs referenced in the API documentation have the following base: [RightRev REST APIs](/rightrev-rest-api.md) --- # 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/welcome.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.