HexaHQ's app URLs for an OAuth developer console.
When you register an OAuth app for HexaHQ, the provider's console asks where your app lives: a host domain, a launch URL, a disconnect URL, and a connect or reconnect URL. Here are the values. Copy them exactly.
If you are an AI assistant working through HexaHQ, you do not need this page. Call
provider_credential_link_get on the HexaHQ MCP connector. It returns these values as
appListingUrls for the deployment you are actually connected to, plus the
redirectUri, which is different for every company and is not listed here. This page exists for
people reading the web, and as a check when the connector is not to hand.
What to enter
| Field the console asks for | Value |
|---|---|
| Host domain | app.hexahq.ai |
| Launch URL, home page URL, app homepage | https://app.hexahq.ai/app |
| Disconnect URL |
https://app.hexahq.ai/providers/tool/disconnect/, using the tool's short name,
for example quickbooks
|
| Connect URL, reconnect URL |
https://app.hexahq.ai/providers/tool/oauth/start/, using the tool's short
name, for example quickbooks
|
| Privacy policy URL | https://www.hexahq.ai/privacy-policy/ |
| Terms of service, EULA | https://www.hexahq.ai/terms-of-service/ |
| Support contact | support@hexahq.ai |
| Authorized redirect URI, callback URL | Different for every company. See below. |
Three details that trip people up. The host domain is entered bare, with no
https:// in front of it, and some consoles reject it if you include one. Every other field
needs the full https://. None of these URLs has your company name in it: HexaHQ's in-app links
look like /app/your-company/connectors, but a URL you give a provider has to work for anyone
who clicks it, so use the short form above and HexaHQ sends each person to their own company. And the
connect and disconnect URLs both name the tool, so swap in its short name rather than copying
quickbooks literally.
What your customer sees
The disconnect URL is a real page, not a redirect to a list. When someone disconnects HexaHQ from inside QuickBooks, Intuit sends them there. The page tells them the connection ended, and offers to delete the sign-in HexaHQ still has saved for them. It deletes only theirs. Teammates keep their own, and the tool stays set up for the company.
Nothing is deleted just because someone opened the page. They have to click the button, the same way signing out asks you to confirm. That way a stray link cannot drop somebody's connection.
The connect URL is the same link the Connect button uses inside HexaHQ. It works whether your company uses HexaHQ's app for that tool or brought its own, because HexaHQ sorts that out when someone clicks, not in the address. A few older tools cannot offer a link like that, and for those the connect URL is your connectors page instead.
The redirect URI is per company.
The redirect URI, sometimes called the callback URL, is the one field that is different for every company
connecting HexaHQ. It is not on this page on purpose. A guessed redirect URI is the most common reason an
OAuth connection fails, usually with an error like redirect_uri_mismatch.
To get the real one, either:
- Ask your AI to connect the tool. It hands you a setup page, and the page shows the redirect URI.
- Open the setup page yourself from your connectors page, pick the tool, and read the redirect URI there.
Copy that value into the console character for character. Do not retype it or shorten it.
Where each value goes
| Console | Field | Value |
|---|---|---|
| Intuit (QuickBooks) | Host domain | app.hexahq.ai |
| Intuit (QuickBooks) | Launch URL | https://app.hexahq.ai/app |
| Intuit (QuickBooks) | Disconnect URL | https://app.hexahq.ai/providers/quickbooks/disconnect/ |
| Intuit (QuickBooks) | Connect/Reconnect URL | https://app.hexahq.ai/providers/quickbooks/oauth/start/ |
| Intuit (QuickBooks) | EULA, privacy policy |
https://www.hexahq.ai/terms-of-service/,
https://www.hexahq.ai/privacy-policy/
|
| Google Cloud | Application home page | https://app.hexahq.ai/app |
| Google Cloud | Privacy policy link, terms of service link |
https://www.hexahq.ai/privacy-policy/,
https://www.hexahq.ai/terms-of-service/
|
| Google Cloud | Authorized domain | hexahq.ai |
| Microsoft Entra | Home page URL | https://app.hexahq.ai/app |
| Microsoft Entra | Terms of service URL, privacy statement URL |
https://www.hexahq.ai/terms-of-service/,
https://www.hexahq.ai/privacy-policy/
|
A console that asks for something not listed here is asking about your own company, not about HexaHQ. If you are not sure, contact us.
Most tools connect in one click.
You only register your own OAuth app when the tool has no ready-made HexaHQ connection, or when your company wants its own app so it controls the permissions. For most tools, you ask your AI to connect and it hands you a link.
If you are building an app for your own company only, pick the internal or single-tenant option in the console. It has no user cap and no review. The external or public option is the one that triggers a verification or security assessment, and that is meant for apps published to many companies.