Product
Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing
Developers

GET STARTED

API DirectoryBrowse 10,000+ APIs Ready For AI Agent IntegrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI Readiness using our scorecardArazzo UIVisualize Arazzo Workflows As Interactive DocumentationArazzo EditorBuild And Edit Multi-Step API Workflows Visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
Resources
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
Resources
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Typeform API
Typeform API logo

Typeform API

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer30 EndpointsREST

For Agents

Programmatically create a form, list forms. Covers 30 operations with bearer authentication.

Use for: I need to a form, I want to forms, Search for a form, Find all a form

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Typeform API allows you to create and manage forms, collect responses, configure webhooks, manage themes, images, and workspaces programmatically. The API exposes 30 endpoints secured with bearer authentication.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Typeform API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Typeform 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftypeform.com%2Ftypeform" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftypeform.com%2Ftypeform" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Typeform API.

Create a form

List forms

Get a form

Update a form

Patch a form

Delete a form

Use Cases

Patterns agents use Typeform API for, with concrete tasks.

★ Developer Tools Operations

Use the Typeform API to perform developer tools operations programmatically. The API provides 30 endpoints covering core functionality including create a form, list forms, get a form.

Call POST /forms to create a form

Automated Account Management

Automate account operations by combining multiple Typeform API endpoints. Agents can list forms and then get a form in a single workflow.

Call GET /forms to list forms, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Typeform API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'create a form', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

30 endpoints — typeform api allows you to create and manage forms, collect responses, configure webhooks, manage themes, images, and workspaces programmatically.

METHOD

PATH

DESCRIPTION

POST

/forms

Create a form

GET

/forms

List forms

GET

/forms/{form_id}

Get a form

PUT

/forms/{form_id}

Update a form

PATCH

/forms/{form_id}

Patch a form

DELETE

/forms/{form_id}

Delete a form

GET

/forms/{form_id}/messages

Get form messages

PUT

/forms/{form_id}/messages

Update form messages

POST

/forms

Create a form

GET

/forms

List forms

GET

/forms/{form_id}

Get a form

PUT

/forms/{form_id}

Update a form

PATCH

/forms/{form_id}

Patch a form

DELETE

/forms/{form_id}

Delete a form

GET

/forms/{form_id}/messages

Get form messages

PUT

/forms/{form_id}/messages

Update form messages

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Setup

Wiring the Typeform API by hand means attaching a bearer token on every call, matching each form and message operation to its request shape, and handling responses yourself. Through Jentic you install once, import the Typeform API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Permission scoping

Typeform puts the form id in the URL path (/forms/{form_id}), so a rule can pin your agent to one form: it can read that form and its messages and nothing else. You choose the operations it may call, so destructive ones like deleting or replacing a form are not included unless you add them.

Credential management

Credential isolation

Your Typeform token 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.

Intent-based discovery

Intent-based discovery

Agents search Jentic by intent such as 'create a form' or 'read a form's messages', and Jentic returns the matching Typeform operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

→

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

→

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Typeform API through Jentic.

What authentication does the Typeform API use?

The Typeform API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create a form with the Typeform API?

Yes. Use the POST /forms endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Typeform API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a form through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a form'. Jentic returns the matching Typeform API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Typeform API have?

The Typeform API exposes 30 endpoints covering account, forms, images operations.

Can I limit what my agent is allowed to do with the Typeform API?

Yes. Because you run Jentic One yourself, your own rules decide which Typeform operations and credentials the agent may use. Since Typeform puts the form id in the URL path (/forms/{form_id}), a rule can pin the agent to a single form so it only reads that form and its messages and nothing else. You pick the operations it may call, so destructive ones like deleting or replacing a form stay out of reach unless you add them.

GET STARTED

Start building with Typeform API

Explore with Jentic One
View OpenAPI Document