Forms

Name: Forms API
Brand: Forms
Availability: InStock

✓ Official Vendor SpecMarketingMarketing Automationoauth26 EndpointsREST

For Agents

Create, update, and manage HubSpot lead-capture form definitions that drive contact creation across landing pages, embedded widgets, and pop-up CTAs.

Quickstart

Get started with Forms 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:
"create hubspot form"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Forms API.

Create a new HubSpot form definition with a typed field schema and submit button configuration

Update an existing form's fields, redirect URL, and notification settings without recreating the form

Retrieve a single form by id including its full field schema for client-side rendering

List all forms in the account with paging to power admin dashboards

GET STARTED

Start building with Forms API

Explore with Jentic

View OpenAPI Document

The HubSpot Forms API manages the lead-capture form definitions that power landing pages, embedded widgets, and pop-up CTAs in a HubSpot account. It supports listing forms, retrieving a form by id, creating new form definitions with field configurations, updating their schema and display configuration, and deleting forms that are no longer in use. Forms created here flow directly into the CMS for embedding and into the Contacts CRM as the lead-capture surface that creates and updates contact records on submission.

Use Cases

Patterns agents use Forms API for, with concrete tasks.

★ Programmatic Form Provisioning

Provision lead-capture forms from code so each new campaign launch ships with its tracked form definition rather than a manual click-through. POST /marketing/v3/forms/ accepts a typed field schema, submit button label, and redirect URL, returning the form id you can embed on landing pages or load via the JS embed snippet. Useful for marketing-ops teams managing dozens of campaign forms a quarter.

Call POST /marketing/v3/forms/ with name=Q3 demo request, fieldGroups containing email and firstName fields, and a submitButtonText value.

Form Schema Synchronisation

Keep a form definition in sync with downstream consumers (a custom front-end, a no-code page builder) by retrieving the full schema via GET /marketing/v3/forms/{formId}. The response includes every field group, display config, and submission action, so an agent can render the form server-side or validate inputs against the same schema HubSpot enforces.

Call GET /marketing/v3/forms/{formId} and use the returned fieldGroups array to render an HTML form in your application.

Form Lifecycle Management

Retire forms that are no longer in use to keep the admin UI clean and prevent stale forms from accidentally collecting low-quality leads. Listing forms with paging, then DELETE /marketing/v3/forms/{formId} for the obsolete ones, gives marketing-ops a scriptable cleanup path. Useful for end-of-quarter housekeeping.

Call GET /marketing/v3/forms/ to list forms, filter by name pattern, then call DELETE /marketing/v3/forms/{formId} for each obsolete entry.

AI Agent Form Bootstrap via Jentic

An AI agent setting up a new product launch creates the campaign's lead-capture form by searching Jentic for HubSpot form-creation operations, loading the schema for POST /marketing/v3/forms/, and submitting the field configuration. Jentic stores the OAuth credential so the agent never handles raw tokens, and the search-load-execute flow takes seconds.

Search Jentic for "create hubspot form", load the schema for POST /marketing/v3/forms/, and execute with the field configuration.

Key Endpoints

6 endpoints — the hubspot forms api manages the lead-capture form definitions that power landing pages, embedded widgets, and pop-up ctas in a hubspot account.

METHOD

PATH

DESCRIPTION

GET

/marketing/v3/forms/

List all forms in the account

POST

/marketing/v3/forms/

Create a new form definition

GET

/marketing/v3/forms/{formId}

Retrieve a form by id

PATCH

/marketing/v3/forms/{formId}

Update an existing form

DELETE

/marketing/v3/forms/{formId}

Delete a form

GET

/marketing/v3/forms/

List all forms in the account

POST

/marketing/v3/forms/

Create a new form definition

GET

/marketing/v3/forms/{formId}

Retrieve a form by id

PATCH

/marketing/v3/forms/{formId}

Update an existing form

DELETE

/marketing/v3/forms/{formId}

Delete a form

Why though 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. Agents receive scoped execution access — the raw bearer token never enters the agent's context window.

Intent-based discovery

Agents search Jentic with intents like 'create hubspot form' and Jentic returns the matching operation with its input schema, so the agent calls POST /marketing/v3/forms/ with the right fieldGroups payload without browsing HubSpot docs.

Time to first call

Direct HubSpot integration: 1-2 days for OAuth setup, field schema validation, and embed wiring. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

CRM Contacts

The contact records that form submissions create and update

Choose this when the agent needs to read the contact record produced by a submission.

Complementary

Marketing Campaigns

Attach forms to campaigns for cross-asset reporting

Choose this when the form is part of a multi-asset campaign initiative.

Complementary

CMS Pages

Landing pages that embed the forms created here

Choose this when the form needs to be hosted on a HubSpot landing page.

Alternative

Typeform

Conversational form builder with richer interactive flows

Choose Typeform when the form needs branching logic and a conversational UX beyond HubSpot's native field types.

FAQs

Specific to using Forms API through Jentic.

What authentication does the Forms API use?

The API accepts HubSpot OAuth 2.0 access tokens or private app tokens (legacy schemes oauth2_legacy and private_apps_legacy) sent as Bearer in the Authorization header. Through Jentic, the token is stored encrypted in MAXsystem so the agent never sees the raw secret.

Can I create a form with custom fields via the API?

Yes. POST /marketing/v3/forms/ accepts a fieldGroups array where each group lists the typed fields (text, email, dropdown, etc.) to render. Field metadata such as required status and validation rules are set per field.

How do I render a HubSpot form on my own front-end?

Call GET /marketing/v3/forms/{formId} to retrieve the full field schema, then render the fields client-side and POST submissions to HubSpot's submission endpoint. The schema includes labels, types, and validation hints.

What are the rate limits for the Forms API?

Account-level limits are 100 requests per 10 seconds across HubSpot's authenticated APIs, with daily caps that depend on the subscription tier. Cache form definitions in your application to reduce repeat reads.

How do I create a form through Jentic?

Run pip install jentic, search for "create hubspot form", load the schema for POST /marketing/v3/forms/, and execute with name and fieldGroups. Sign up at https://app.jentic.com/sign-up to get an ak_* key.

Does deleting a form remove its historical submissions?

No. DELETE /marketing/v3/forms/{formId} removes the form definition so it can no longer accept new submissions, but historical submissions remain attached to the contact records they created or updated.