canonical: https://jentic.com/apis/hubspot.com/hubspot-account-info

# HubSpot Account Account Info

The HubSpot Account Info API exposes account-level metadata and private app API usage for a HubSpot portal. GET /account-info/v3/details returns the portal id, time zone, currency, company name, and whether the account is sandbox, while GET /account-info/v3/api-usage/daily/private-apps returns the day's call counts for each private app on the portal. The endpoints are designed for ops dashboards and quota monitoring rather than data manipulation. Both calls accept an OAuth 2.0 access token or a private app token in the private-app header.

## For AI agents

Read HubSpot portal metadata and the daily private-app API usage so agents and dashboards can verify the account context and stay within rate limits.

## Scope

Does not modify portal settings, read CRM records, or write any data - use only to read HubSpot portal metadata and private-app daily API usage.

## Capabilities

- Retrieve a HubSpot portal's id, currency, time zone, and company name
- Determine whether the connected account is a sandbox or production portal
- Read the daily API call counts for each private app on the portal
- Detect when a private app is approaching its daily call limit
- Verify the connected account before running scoped CRM operations

## Use cases

### Display the connected portal in an admin UI

When an integration shows which HubSpot account it is currently connected to, GET /account-info/v3/details supplies the portal id, company name, currency, time zone, and sandbox flag in one call. This avoids confusion when a user has access to multiple portals and removes the need to hand-enter portal metadata.

Example prompt: Call GET /account-info/v3/details and render portalId, companyName, timeZone, and accountType in the admin header

### Monitor private app daily quota

Private apps on a HubSpot portal share a daily API call limit. GET /account-info/v3/api-usage/daily/private-apps returns the day's call count per private app so a monitoring job can alert when usage crosses a threshold. The response is keyed by private app so multi-app portals can attribute usage accurately.

Example prompt: Call GET /account-info/v3/api-usage/daily/private-apps every hour and emit an alert when any private app's currentUsage exceeds 80% of its dailyLimit

### Agent integration via Jentic

An ops agent investigating rate-limit errors can pull current usage and account context in two calls. Through Jentic the agent searches for the account info operations, loads the schemas, and executes them in sequence. The HubSpot credential never leaves your Jentic One instance.

Example prompt: Search Jentic for 'get hubspot account details', load GET /account-info/v3/details, then load and execute GET /account-info/v3/api-usage/daily/private-apps to gather full context

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /account-info/v3/details | Retrieve account details for the connected HubSpot portal |
| GET | /account-info/v3/api-usage/daily/private-apps | Retrieve daily API usage per private app |

## Key resources

- **Details** — Read HubSpot portal-level metadata such as id, currency, and time zone
- **Usage** — Read daily private-app API usage counts for the connected portal

## Why Jentic

- **Setup:** Wiring the HubSpot Account Info API by hand means handling both OAuth and app-token auth against api.hubapi.com and reading portal metadata and daily usage figures yourself. Through Jentic you install once, import Account Account Info from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Both operations read portal metadata and private-app usage and take no resource id, so limit the agent to the operations it needs, such as reading portal details or daily API usage. This API is read-only, so there are no write or delete calls to grant.
- **Credential handling:** Your HubSpot credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check hubspot private app daily API usage', and Jentic returns GET /account-info/v3/api-usage/daily/private-apps with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot Audit Logs** — Audit Logs returns login activity and security history for the same portal
- **HubSpot OAuth** — OAuth endpoints return token metadata and refresh access tokens used here
- **HubSpot Auth API** — Equivalent OAuth and account introspection endpoints under hubapi.com

## FAQ

### What authentication does the HubSpot Account Info API use?

The spec lists two security schemes: OAuth 2.0 access tokens and a private app token sent in the private-app header. Either credential type can call both endpoints. Through Jentic the credential is stored encrypted in the vault and the agent receives only a scoped session token.

### Can I tell if a HubSpot account is a sandbox with this API?

Yes. The response from GET /account-info/v3/details includes an accountType field that distinguishes between standard, sandbox, and developer test accounts, so an integration can branch on environment without hardcoding portal ids.

### What are the rate limits for the HubSpot Account Info API?

The spec does not declare a per-endpoint limit. Account Info calls count against the standard HubSpot per-account limit of around 100 requests per 10 seconds for OAuth and private apps, plus the daily call cap surfaced by the private-apps usage endpoint itself.

### How do I check daily API usage for a private app through Jentic?

Search Jentic for 'check hubspot private app daily API usage', load the schema for GET /account-info/v3/api-usage/daily/private-apps, and execute it. Jentic returns the JSON list with per-private-app currentUsage and dailyLimit values.

### Does this API expose CRM data such as contacts or deals?

No. Account Info is read-only metadata about the portal and its API usage. Use the HubSpot CRM API for contacts, companies, deals, and other CRM objects.

### Can I limit what my agent is allowed to do with the HubSpot Account Info API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. This API is read-only, so you can allow just the calls you need, such as reading portal details from GET /account-info/v3/details or the daily private-app usage from GET /account-info/v3/api-usage/daily/private-apps, and withhold the other. Neither operation takes a resource id and there are no write or delete calls, so a scoped agent can read account metadata and usage counts without touching any portal settings or CRM data.