> For the complete documentation index, see [llms.txt](https://documentation.carbonregistry.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.carbonregistry.com/documentation/carbonregistry.com/api/apps/creating-icr-apps/registering-an-icr-app/callback-urls.md).

# Callback URLs

When you register an ICR App, you can specify an allowlist of callback URLs. When users install your ICR App, they are redirected to the first callback URL in the allowlist, unless the `redirectUri` query parameter is non-empty. If it is non-empty the `redirectUri` is used but only if it matches an allowed callbackURL from the callback URL list. If it does not match any, the first callback URL is used. If additional setup is required after installation, you can use this URL to tell users what steps to take next.

***

**Warning**: When ICR redirects users to the callback URL, it includes an `installationId` query parameter. Bad actors can hit this URL with a spoofed `installationId`. Therefore, you should not rely on the validity of the `installationId` parameter. Instead, you should generate an organization access token for the organization where the app was installed and then check that the installation is associated with that organization. For more information, see "[Generating an installation access token for an ICR App](/documentation/carbonregistry.com/api/apps/authentication/authenticate-as-an-installation.md)."

***

For more information about registering an ICR App, see "[Registering an ICR App](/documentation/carbonregistry.com/api/apps/creating-icr-apps/registering-an-icr-app.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.carbonregistry.com/documentation/carbonregistry.com/api/apps/creating-icr-apps/registering-an-icr-app/callback-urls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.