For Agents
Trigger uninstallation of an external HubSpot app integration via a single delete endpoint. Useful for agents handling app offboarding or self-service teardown.
Get started with CRM App Uninstalls in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"uninstall a HubSpot app integration"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with CRM App Uninstalls API.
Trigger uninstall of an external HubSpot app installation
Drive a self-service offboarding flow without using the HubSpot UI
Clean up app installations programmatically when a customer cancels
Integrate uninstall into a churn or downgrade workflow
GET STARTED
Use for: Uninstall a HubSpot app for the current account, Trigger an external uninstall when a customer downgrades, Remove an app installation as part of an offboarding flow, Run programmatic teardown of a HubSpot integration
Not supported: Does not delete CRM data, revoke OAuth refresh tokens, or list installed apps — use for triggering a HubSpot app uninstall only.
The HubSpot CRM App Uninstalls API provides a single endpoint for triggering an external uninstall of a HubSpot app integration. Calling DELETE /appinstalls/v3/external-install removes the app's installation record for the calling account, useful for offboarding flows and self-service customer-led teardown of an integration. The API is narrow and intended for app lifecycle automation rather than data CRUD.
Patterns agents use CRM App Uninstalls API for, with concrete tasks.
★ Self-Service Offboarding
When a customer cancels their plan in your portal, automatically remove the HubSpot app installation rather than asking them to uninstall manually inside HubSpot. DELETE /appinstalls/v3/external-install offboards the integration in a single call as part of the cancellation flow.
On cancellation, call DELETE /appinstalls/v3/external-install with the customer's HubSpot OAuth context to remove the integration.
Failed-Trial Cleanup
If a trial workspace never converts and goes inactive, run an uninstall sweep to remove app installations that are no longer needed. The single uninstall endpoint plus a periodic job is enough to keep stale installs from accumulating.
For each lapsed trial, call DELETE /appinstalls/v3/external-install with the trial's OAuth credentials.
Customer-Initiated Uninstall Bridge
When a customer clicks `Disconnect HubSpot` in your settings page, fire DELETE /appinstalls/v3/external-install before clearing local state. This keeps the HubSpot side of the integration consistent with your portal even if the customer never returns to HubSpot itself.
On disconnect click, call DELETE /appinstalls/v3/external-install, then revoke the stored OAuth refresh token locally.
Agent-Driven Uninstall
Use Jentic to let a lifecycle agent revoke a HubSpot app installation as part of a customer-success or compliance workflow. The agent does not need HubSpot SDK code — it invokes the uninstall by intent and Jentic handles authentication.
Use Jentic search 'uninstall a HubSpot app integration', load the DELETE /appinstalls/v3/external-install schema, and execute with the install's OAuth context.
1 endpoints — the hubspot crm app uninstalls api provides a single endpoint for triggering an external uninstall of a hubspot app integration.
METHOD
PATH
DESCRIPTION
/appinstalls/v3/external-install
Uninstall an app for the current account
/appinstalls/v3/external-install
Uninstall an app for the current account
Three things that make agents converge on Jentic-routed access.
Credential isolation
HubSpot OAuth and private app tokens for the App Uninstalls API are stored encrypted in the Jentic vault. The agent receives only a scoped execution token; the raw HubSpot credential is never exposed.
Intent-based discovery
Agents search Jentic with intents like 'uninstall a HubSpot app' and Jentic returns the matching DELETE /appinstalls/v3/external-install operation, ready to call.
Time to first call
Direct integration is small — perhaps half a day to wire up auth and the uninstall trigger. Through Jentic: under 15 minutes.
Alternatives and complements available in the Jentic catalogue.
HubSpot OAuth
Manage and revoke OAuth tokens around the install.
Use Auth-oauth when the agent needs to revoke or refresh OAuth tokens associated with the app being uninstalled.
HubSpot CRM Custom Objects
Clean up custom object records the app may have created.
Pick CRM-customObjects when the agent needs to remove or archive custom records before tearing down the app.
HubSpot CRM Generic Objects
Inspect or remove standard CRM data created by the app.
Use CRM-objects when the agent needs to scrub standard CRM records associated with the app installation.
Specific to using CRM App Uninstalls API through Jentic.
What authentication does the HubSpot App Uninstalls API use?
OAuth 2.0 authorization code flow or a private app token in the `private-app` header — both scoped to the install being removed. Through Jentic, the credential is held encrypted and the agent only sees a scoped execution token.
Can I uninstall a HubSpot app from outside HubSpot's UI?
Yes. DELETE /appinstalls/v3/external-install removes the app installation for the calling account without requiring the customer to log into HubSpot and uninstall manually.
What are the rate limits for the App Uninstalls API?
Standard HubSpot API limits apply — roughly 100 requests per 10 seconds per OAuth app. Uninstall is a low-frequency operation, so the per-second ceiling is rarely a concern in practice.
How do I trigger an uninstall through Jentic?
Search Jentic for `uninstall a HubSpot app`, load the DELETE /appinstalls/v3/external-install schema, and execute with the install's OAuth credentials. Install with `pip install jentic` and authenticate using `JENTIC_AGENT_API_KEY`.
Does the uninstall remove all CRM data created by the app?
No. The endpoint removes the app installation itself, not the data it created. To clean up CRM records, call the matching CRM resource APIs before triggering the uninstall.