For Agents
Create and manage JotForm forms, questions, and properties, retrieve and post submissions, build reports, and register webhooks so agents can sync form data into CRMs, warehouses, or downstream workflows.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JotForm 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.
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 | shStep 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.
What an agent can do with JotForm API.
Create, clone, update, and delete forms programmatically
Add, modify, and remove individual questions on a form
Read and write form-level properties such as theme and behaviour settings
Retrieve form submissions or post new submissions on behalf of the user
GET STARTED
Use for: I need to list every JotForm form on the account, Create a new JotForm form for an event registration, Get all submissions for form 232101010101010 in the last 30 days, Delete the test form I created yesterday
Not supported: Does not handle email-only newsletter sending, full marketing automation, or hosted analytics dashboards — use for form definition, submission collection, and submission-driven webhook flows only.
JotForm is a hosted form-builder used to collect submissions for surveys, registrations, payments, and lead capture. The API exposes the full surface — managing forms, questions, properties, submissions, reports, folders, labels, and webhooks — so that external systems can build forms programmatically, sync responses, and react to submissions in near real time. It is the right pick when an application owns a CRM, support tool, or data warehouse that needs form data without manual export.
Generate reports and folder structures to organise large form portfolios
Register and remove webhooks so external systems get pinged on each new submission
Manage labels to tag and group resources across the JotForm account
Patterns agents use JotForm API for, with concrete tasks.
★ Sync submissions to a CRM
Sales teams collecting leads through JotForm forms can keep their CRM up to date by polling GET /form/{formID}/submissions or, better, by registering a webhook with POST /form/{formID}/webhooks. Each new submission is pushed to the configured URL, the integration parses the answers, and creates a contact in the CRM. This avoids the manual CSV export workflow that plagues form-driven funnels.
Call POST /form/{formID}/webhooks with target URL https://example.com/jotform-hook so each new submission triggers a downstream CRM create
Programmatic form creation at scale
Agencies and SaaS products that ship a JotForm-backed form per customer can create forms via POST /form and configure questions and properties through the form-scoped endpoints. This supports a templated approach: a base form spec is rendered into a JotForm definition, customised per tenant, and deployed without manual UI clicks. POST /form/{formID}/clone is also available when a single template is the source of truth.
Call POST /form to create a base form, POST /form/{formID}/questions to add tenant-specific fields, then POST /form/{formID}/properties to set the theme
Submission-driven analytics and reports
Operations teams running ongoing surveys can pull submissions across all forms with GET /user/submissions and feed the JSON response into a warehouse. JotForm's report endpoints (POST /form/{formID}/reports) also let you generate built-in summary reports without bringing the data out — useful when the response volume is small enough that the JotForm UI is sufficient.
Call GET /user/submissions paginated by limit and offset, transform each record, and load into a Snowflake table for weekly reporting
Account-level housekeeping
Admins managing busy JotForm accounts can audit and clean up forms, folders, and labels via the API. GET /user/forms lists every form, DELETE /form/{formID} removes the stale ones, and folder and label endpoints reorganise what remains. Combined with GET /user/usage, this supports plan-aware tidy-ups before quota limits hit.
Call GET /user/forms, identify forms with zero submissions older than 90 days, and call DELETE /form/{formID} on each
Agent-driven form orchestration via Jentic
An AI assistant building or maintaining customer forms can drive JotForm through Jentic without ever touching the apiKey. The agent expresses intent, Jentic resolves to the right operation (POST /form, POST /form/{formID}/webhooks, etc.), injects the apiKey query parameter, and returns the response. This keeps the long-lived JotForm credential out of the agent's reasoning context.
Use Jentic to search 'create a JotForm form', load POST /form, and execute it with the supplied form definition and API key from the vault
57 endpoints — jotform is a hosted form-builder used to collect submissions for surveys, registrations, payments, and lead capture.
METHOD
PATH
DESCRIPTION
/user/forms
List the user's forms
/form
Create a new form
/form/{formID}/submissions
Get submissions for a form
/form/{formID}/submissions
Add a submission to a form
/form/{formID}/webhooks
Register a webhook for a form
/form/{formID}/clone
Clone a form
/submission/{submissionID}
Get a single submission
/user/usage
Get account usage and quota
/user/forms
List the user's forms
/form
Create a new form
/form/{formID}/submissions
Get submissions for a form
/form/{formID}/submissions
Add a submission to a form
/form/{formID}/webhooks
Register a webhook for a form
Three things that make agents converge on Jentic-routed access.
Credential isolation
JotForm API keys are stored encrypted in the Jentic vault. Jentic appends the apiKey query parameter at request time, so the long-lived credential never enters the agent's prompt, chat history, or external logs.
Intent-based discovery
Agents search Jentic with intents like 'create a form', 'list submissions', or 'register a webhook' and Jentic returns the matching JotForm operation with its input schema, replacing manual reading of api.jotform.com/docs.
Time to first call
Direct JotForm integration: 1-2 days to wire up auth, pagination, webhook handling, and rate-limit handling. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using JotForm API through Jentic.
What authentication does the JotForm API use?
The JotForm API uses an API key passed as the apiKey query parameter on every request. The key is generated from the JotForm dashboard and grants access scoped to the user's forms. Jentic stores the key encrypted and appends it at call time so it never appears in the agent's context.
Can I create a form programmatically?
Yes. POST /form creates a new form, POST /form/{formID}/questions adds fields, and POST /form/{formID}/properties configures theme and behaviour. POST /form/{formID}/clone is also available when an existing form is the better starting point than building from scratch.
What are the rate limits for the JotForm API?
Rate and submission limits depend on the JotForm plan tier — free, Bronze, Silver, Gold, Enterprise — and the spec does not publish a single numeric ceiling. Call GET /user/usage to inspect current consumption against the plan, and check api.jotform.com/docs for the latest tier limits.
How do I receive a notification when a JotForm is submitted?
Register a webhook with POST /form/{formID}/webhooks pointing at your endpoint. JotForm POSTs the submission payload there on each new entry. Use DELETE /form/{formID}/webhooks/{webhookID} to remove the hook when no longer needed.
How do I list every submission across all forms?
Call GET /user/submissions to paginate through submissions across the entire account, rather than calling per-form. Combine with limit and offset query parameters to chunk large result sets for ETL into a warehouse.
How do I sync JotForm to my CRM through Jentic?
Search Jentic for 'register a JotForm webhook', load POST /form/{formID}/webhooks, and execute with your CRM ingestion URL. Jentic injects the apiKey from the vault. Sign up at https://app.jentic.com/sign-up.
/form/{formID}/clone
Clone a form
/submission/{submissionID}
Get a single submission
/user/usage
Get account usage and quota