> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/saas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/saas/developer-guides/api-intro/marketplace-api.md). # Request App API Learn about interacting with the Request app via the API ## Base path and global segment In order to use the Request app API, you need to use the correct global segment. The following are the regional API base paths. Choose the global segment for the region you are in. * [https://na.api.immutacloud.com/marketplace](https://na.api.immutacloud.com/marketplace/) - North America * [https://eu.api.immutacloud.com/marketplace](https://eu.api.immutacloud.com/marketplace/) - European Union * [https://ap.api.immutacloud.com/marketplace](https://ap.api.immutacloud.com/marketplace/) - Asia Pacific If using **Test it** in the Request app API documentation, click `https://{global-segment}.api.immutacloud.com/marketplace` in the endpoint and select your global segment from the dropdown. Once you plug in your PAT, the endpoint will run and complete the actions within your Request app. {% hint style="danger" %} Your Request app data only exists in the same global segment as your Govern app. If you use the wrong global segment in your API call, you will receive the following response: ```json { "message": "Not authenticated.", "error": "Unauthorized", "statusCode": 401 } ``` {% endhint %} ## Authentication See instructions for generating your personal access token (PAT) on the [Authentication page](/saas/developer-guides/api-intro/authentication.md). To use your generated PAT, insert it as the Bearer token for your API calls: ``` curl -L \ --url '{correct base path from above}/api/access-agreement' \ --header 'Authorization: Bearer ' ``` Or, if using "Test it" in the Request app API documentation, include it in the bearer token in the authentication section:

Authentication for testing

### Delete a PAT In the Request app, 1. Navigate to the [**Personal Access Tokens** page](https://app.nonprod.immutacloud.com/marketplace/personal-access-tokens). 2. Select the **more actions** icon for the PAT you want to delete. 3. Select **Delete token** and click **Delete** in the modal. ## Download the Request app OpenAPI YAML Download the Request app OpenAPI spec to import it into Postman or use a client generator tool to parse the OpenAPI definition to automatically produce client-side code. --- # 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://documentation.immuta.com/saas/developer-guides/api-intro/marketplace-api.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.