HubSpot User Provisioning
Browse all Hubspot APIs✓ Official Vendor SpecIdentity AuthDirectory Servicesoauth2,apiKey7 EndpointsREST
For Agents
List HubSpot users, teams, and roles; provision new users; update an individual user's role; and offboard users from the portal.
Use for: I need to invite a new sales rep to HubSpot, Remove an offboarded employee from HubSpot, List all users on the HubSpot account, Get the role and team for a specific HubSpot user
Not supported: Does not configure SSO, set permission scopes, or manage app-level OAuth installs — use for HubSpot user, role, and team directory operations only.
The HubSpot User Provisioning API manages the user directory of a HubSpot account: who has a seat, what role they hold, and which team they belong to. It supports inviting and removing users, fetching the role and team rosters, and updating an individual user's role assignment. Identity providers and HRIS systems use it to keep HubSpot's seat allocation in sync as people join, change teams, or leave the company.
Install Jentic One Beta
Connect the HubSpot User Provisioning to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HubSpot User Provisioning, 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 HubSpot User Provisioning API.
List every user with a seat on the HubSpot account
Invite a new user to the HubSpot account with a specific role
Retrieve a single user record by user ID
Update a user's role assignment without recreating the user
Remove a user from the HubSpot account to revoke access
List the teams configured on the portal for assignment
List the roles available on the portal for assignment
Use Cases
Patterns agents use HubSpot User Provisioning API for, with concrete tasks.
★ HRIS to HubSpot user sync
Keep HubSpot's seat list aligned with the source-of-truth HR system by reading new joiners and leavers nightly and pushing them through this API. New hires receive an invite with the correct role, and offboarded users are removed the day they leave so revoked access is enforced without manual cleanup.
For each new joiner, POST /settings/v3/users/ with email and roleId; for each leaver, DELETE /settings/v3/users/{userId} to remove the seat.
Role rebalancing during a reorg
When sales territories or pods are restructured, update many users' role assignments at once without having to recreate accounts. Reading the role list first and patching each user keeps team membership and audit history intact while shifting permissions to the new structure.
Call GET /settings/v3/users/roles to find the new role IDs, then iterate over affected users with PUT /settings/v3/users/{userId} to set the new roleId.
Audit of HubSpot seat usage
Generate a periodic seat audit by listing every user and joining the result against the role and team rosters to surface seats that no longer match an active employee or that hold a role richer than required. Finance and security teams use the same join to confirm that paid seat counts match contract terms.
Call GET /settings/v3/users/, GET /settings/v3/users/roles, and GET /settings/v3/users/teams, then merge the records and flag any user whose role exceeds their job function.
Agent-driven onboarding through Jentic
An onboarding agent triggered by an HRIS new-hire event uses Jentic to find the HubSpot user invite operation, loads the schema, and provisions the seat with the right role and team. Jentic's vault holds the HubSpot OAuth token so the same agent can run safely against multiple HubSpot portals in a multi-tenant setup.
Through Jentic, search 'invite a HubSpot user', load the schema for POST /settings/v3/users/, and execute it with the new hire's email and the AE roleId.
Key Endpoints
7 endpoints — the hubspot user provisioning api manages the user directory of a hubspot account: who has a seat, what role they hold, and which team they belong to.
METHOD
PATH
DESCRIPTION
GET
/settings/v3/users/
List all users on the portal
POST
/settings/v3/users/
Invite a new user to the portal
GET
/settings/v3/users/{userId}
Retrieve a single user record
PUT
/settings/v3/users/{userId}
Update a user's role assignment
DELETE
/settings/v3/users/{userId}
Remove a user from the portal
GET
/settings/v3/users/roles
List available roles
GET
/settings/v3/users/teams
List configured teams
GET
/settings/v3/users/
List all users on the portal
POST
/settings/v3/users/
Invite a new user to the portal
GET
/settings/v3/users/{userId}
Retrieve a single user record
PUT
/settings/v3/users/{userId}
Update a user's role assignment
DELETE
/settings/v3/users/{userId}
Remove a user from the portal
GET
/settings/v3/users/roles
List available roles
GET
/settings/v3/users/teams
List configured teams
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
HubSpot OAuth and private-app tokens are stored encrypted in the Jentic MAXsystem vault. The provisioning agent receives only an execution handle so the raw Bearer token never enters its prompt context.
Intent-based discovery
Agents search by intent like 'invite a HubSpot user' or 'remove a HubSpot user' and Jentic returns the matching User Provisioning operation with its input schema, including the userId and roleId fields.
Time to first call
Direct integration: 2-3 days for OAuth, role-ID lookup, and idempotent retry on invite. Through Jentic: under 1 hour — search, load, execute the invite or delete operation.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using HubSpot User Provisioning API through Jentic.
What authentication does the HubSpot User Provisioning API use?
It accepts HubSpot OAuth 2.0 tokens and private-app tokens passed as a Bearer header. Through Jentic the credential is held in the encrypted MAXsystem vault and injected at execution time, so the agent provisioning users never sees the raw token.
Can I invite a user with a specific role and team?
Yes. POST /settings/v3/users/ accepts the email plus the roleId returned from GET /settings/v3/users/roles and the primary team from GET /settings/v3/users/teams, so invites land with the correct permissions from day one.
What are the rate limits for this API?
HubSpot's standard public API limits apply: 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for private apps. For nightly HRIS sync of large workforces, throttle the inviter loop to stay under that window.
How do I offboard a user through Jentic?
Search Jentic for 'remove a HubSpot user', load the schema for DELETE /settings/v3/users/{userId}, and execute it with the userId. The seat is freed and the user can no longer sign in to the portal.
Does this API replace SCIM provisioning?
It can — the create, update, and delete operations cover the lifecycle most identity providers need to drive HubSpot. Use this API when your IdP does not have a native HubSpot SCIM connector, or when you need finer control than the SCIM mapping allows.
Can I change a user's role without recreating the user?
Yes. PUT /settings/v3/users/{userId} updates the roleId in place, preserving the user's history, owned records, and login. Recreate the user only when the email itself needs to change.
GET STARTED