HubSpot Account Test Child Api
Browse all HubSpot APIs✓ Official Vendor SpecDeveloper ToolsMonitoring Observabilityoauth2, apiKey4 EndpointsREST
For Agents
Read HubSpot portal login activity, daily API usage, account details, and security events through four GET endpoints under /account-info/v3.
Use for: I need to verify the current HubSpot portal context, Get today's API usage for my HubSpot account, Retrieve recent login activity on the portal, List security events such as password changes for the account
Not supported: 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.
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.
Install Jentic One Beta
Connect the Account Test Child Api to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Account Test Child Api, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Account Test Child Api.
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
Patterns agents use Account Test Child Api for, with concrete tasks.
★ 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.
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.
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.
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 the Jentic vault.
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
4 endpoints — 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.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Legacy OAuth and legacy private app tokens are stored encrypted in the Jentic vault. Calls run through scoped session tokens so the raw HubSpot credential never enters the agent's context.
Intent-based discovery
Agents search Jentic with intents like 'check hubspot daily api usage' and Jentic returns the matching GET /account-info/v3/api-usage/daily operation with its input schema.
Time to first call
Direct integration: an hour or two to wire legacy auth and parse responses. Through Jentic: under 15 minutes — search, load, execute against the four read endpoints.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Account Test Child Api through Jentic.
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.
GET STARTED