canonical: https://jentic.com/apis/hubspot.com/hubspot-account-test-child

# HubSpot Account Test Child API

The HubSpot Account Test Child API is a small surface that returns account-level activity, daily API usage, account details, and security events for a HubSpot portal. The four endpoints under /account-info/v3 are GET-only and read the same portal metadata used by ops dashboards and security tooling. Authentication uses the legacy OAuth scheme or a legacy private app token in the private-app-legacy header. The API is read-only and is intended for monitoring rather than configuration.

## For AI agents

Read HubSpot portal login activity, daily API usage, account details, and security events through four GET endpoints under /account-info/v3.

## Scope

Does not modify portal settings, write audit entries, or read CRM records - use only to read HubSpot portal metadata, daily API usage, and login or security activity.

## Capabilities

- Retrieve recent successful login activity for a HubSpot portal
- Read the day's API call count and limit for the portal
- Read portal-level account details such as id, currency, and time zone
- Read security history events such as password changes and 2FA updates
- Verify the connected portal context before running scoped CRM operations

## Use cases

### Daily quota dashboard

An ops dashboard surfaces the current day's HubSpot API usage for the portal so engineers can see when integrations are about to hit the daily call limit. GET /account-info/v3/api-usage/daily returns the day's total against the limit, and GET /account-info/v3/details enriches the panel with portal id and time zone.

Example prompt: Call GET /account-info/v3/api-usage/daily once per hour and render currentUsage versus dailyLimit on the dashboard

### Pre-flight portal verification

Before running a destructive batch operation, an integration calls GET /account-info/v3/details to confirm the portal id, the account type, and the currency match expectations. This guards against running a bulk update against the wrong portal when a credential has been swapped.

Example prompt: Call GET /account-info/v3/details and abort the run unless portalId equals the configured target portal id

### Lightweight security review

Smaller teams can run a weekly security review by reading login activity and security events for the portal. GET /account-info/v3/activity/login returns recent logins and GET /account-info/v3/activity/security returns password and 2FA events. The combined output forms a digest that surfaces unexpected access patterns.

Example prompt: Call GET /account-info/v3/activity/login and GET /account-info/v3/activity/security for the past week and email the digest to the security channel

### Agent integration via Jentic

An agent can answer 'are we close to the HubSpot daily limit' by pulling the usage endpoint through Jentic. The agent searches for the operation, loads the schema, and executes the call. The HubSpot credential never leaves your Jentic One instance.

Example prompt: Search Jentic for 'check hubspot daily API usage', load GET /account-info/v3/api-usage/daily, and execute to retrieve currentUsage and dailyLimit

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /account-info/v3/activity/login | Retrieve login activity |
| GET | /account-info/v3/api-usage/daily | Retrieve daily API usage and limits |
| GET | /account-info/v3/details | Retrieve account details |
| GET | /account-info/v3/activity/security | Retrieve security activity |

## Key resources

- **Activity** — Read login activity and security history for the portal
- **Usage** — Read the day's API call count and daily limit
- **Details** — Read portal-level account metadata

## Why Jentic

- **Setup:** Wiring this HubSpot account API by hand means handling both OAuth and app-token auth against api.hubapi.com and reading portal metadata, usage, and activity yourself. Through Jentic you install once, import Account Test Child API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Every operation reads portal metadata, usage, or activity and takes 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 daily API usage', and Jentic returns GET /account-info/v3/api-usage/daily with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot Account Info** — Account Info covers a similar surface using the modern oauth2 and private_apps schemes
- **HubSpot Audit Logs** — Audit Logs returns full audit-log entries on top of login and security activity
- **HubSpot OAuth** — Inspect and refresh the access tokens used to call the test child endpoints

## FAQ

### What authentication does the Account Test Child API use?

The spec defines two legacy security schemes: OAuth 2.0 (oauth2_legacy) and a private app token sent in the private-app-legacy header. Both can call all four GET endpoints. Through Jentic the credential is stored encrypted in the vault.

### Can I read today's API usage with this API?

Yes. GET /account-info/v3/api-usage/daily returns the current day's API call count and the daily limit for the connected portal, so a monitoring job can alert when usage approaches the cap.

### What are the rate limits for the Account Test Child API?

The spec does not declare a per-endpoint limit. The endpoints 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 returned by /account-info/v3/api-usage/daily itself.

### How do I check daily HubSpot API usage through Jentic?

Search Jentic for 'check hubspot daily API usage', load the schema for GET /account-info/v3/api-usage/daily, and execute. Jentic returns the JSON body with currentUsage and dailyLimit values for the portal.

### Does this API expose CRM records like contacts and deals?

No. All four endpoints are read-only metadata about the portal, its API usage, and security events. 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 Test Child API?

Yes. Because you self-host Jentic One, your own rules decide which of the four GET operations the agent may call, so you can grant only reading daily API usage (GET /account-info/v3/api-usage/daily) or portal details (GET /account-info/v3/details) while withholding the login and security activity endpoints. Every operation is read-only and takes no resource id, so there are no write or delete calls to grant. Jentic One stores the HubSpot credential encrypted on your instance and injects it only when an allowed operation runs.