123FormBuilder API

Name: 123FormBuilder API API
Brand: 123FormBuilder API
Availability: InStock

★ Only Publicly Available SpecProductivityForms Surveysbearer7 EndpointsREST

For Agents

Read 123FormBuilder forms, list and fetch submissions, inspect field schemas, and remove unwanted submission records via a JWT-authenticated REST API.

Quickstart

Get started with 123FormBuilder API 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:
"list 123formbuilder form submissions"

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

Capabilities

What an agent can do with 123FormBuilder API API.

List every form in the 123FormBuilder account and fetch a specific form's metadata via GET /forms and GET /forms/{formId}

Page through submissions for a form and retrieve a single response by ID through GET /forms/{formId}/submissions and /forms/{formId}/submissions/{submissionId}

Inspect a form's field definitions to understand the response schema before parsing data via GET /forms/{formId}/fields

Remove individual submissions for data hygiene or GDPR requests with DELETE /forms/{formId}/submissions/{submissionId}

GET STARTED

Start building with 123FormBuilder API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for 123FormBuilder API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for 123FormBuilder API, keeping it validated and agent-ready. The 123FormBuilder API gives programmatic access to forms, submissions, fields, and form groups built in the 123FormBuilder no-code form designer. It is a read-focused REST API authenticated with a JWT bearer token, exposing seven endpoints for listing and retrieving forms and their schemas, paging through submission data, and deleting submission records when they are no longer needed. It suits teams that build their forms in the 123FormBuilder UI and want to pull responses into downstream systems, dashboards, or AI agents without polling the web app.

Use Cases

Patterns agents use 123FormBuilder API API for, with concrete tasks.

★ Sync form submissions into a CRM

Pull responses from a 123FormBuilder lead capture, contact, or registration form and push each entry into a CRM as a new contact or deal. The agent calls GET /forms/{formId}/submissions on a schedule, deduplicates against the last seen submission ID, and uses GET /forms/{formId}/fields to map each field to a CRM property. Suitable for teams running marketing or sales forms in 123FormBuilder who need entries to land in HubSpot, Salesforce, or a similar system without manual export.

Fetch all submissions for form 98765 created in the last 24 hours, map each field using the form's field schema, and create one CRM contact per submission

Build a submissions dashboard or report

Aggregate response volume, completion patterns, and field-level answers across one or more 123FormBuilder forms for a reporting dashboard. The agent walks GET /forms to discover available forms, calls GET /forms/{formId}/submissions per form, and joins the data against GET /forms/{formId}/fields for human-readable field labels. Useful for ops, marketing, or research teams who run multiple forms and need a single view of activity.

Pull submission counts for every form in the account over the last 30 days and produce a CSV with form name, submission count, and last submission date

GDPR and data-hygiene cleanup

Remove specific form submissions on request, for example a data subject erasure request, a duplicate test entry, or a spam submission flagged by another system. The agent locates the submission via GET /forms/{formId}/submissions or by ID, confirms the match, and calls DELETE /forms/{formId}/submissions/{submissionId} to remove it. Designed for support, legal, or compliance teams who need a programmatic way to honour deletion requests without logging into the 123FormBuilder UI.

Find the submission on form 45678 with email user@example.com and call DELETE /forms/45678/submissions/{submissionId} to remove it

Agent-driven form response triage

An AI agent monitors a 123FormBuilder form and triages each new submission, for example routing support requests, scoring leads, or escalating urgent inquiries. Through Jentic, the agent searches for the right operation, loads the schema for GET /forms/{formId}/submissions, and executes the call with a Jentic-managed bearer token. The agent then reads the field schema, applies its own classification logic, and triggers downstream actions such as sending a Slack alert or creating a CRM record.

Through Jentic, search for 'list 123formbuilder submissions', load the schema, execute GET /forms/{formId}/submissions for form 12345, and post a summary of new entries to a Slack channel

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for 123formbuilder api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/forms

List forms in the account

GET

/forms/{formId}

Get a specific form's metadata

GET

/forms/{formId}/submissions

List submissions for a form

GET

/forms/{formId}/submissions/{submissionId}

Retrieve a single submission

DELETE

/forms/{formId}/submissions/{submissionId}

Delete a submission

GET

/forms/{formId}/fields

List a form's field definitions

GET

/groups

List form groups

GET

/forms

List forms in the account

GET

/forms/{formId}

Get a specific form's metadata

GET

/forms/{formId}/submissions

List submissions for a form

GET

/forms/{formId}/submissions/{submissionId}

Retrieve a single submission

DELETE

/forms/{formId}/submissions/{submissionId}

Delete a submission

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The 123FormBuilder JWT bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access at call time, so the raw JWT never enters the agent's prompt or context window.

Intent-based discovery

Agents search Jentic by intent, for example 'list 123formbuilder submissions' or 'delete a form response', and Jentic returns the matching 123FormBuilder operation with its input schema so the agent can call the right endpoint without browsing docs.

Time to first call

Direct 123FormBuilder integration: 0.5-1 day to wire up auth, pagination, field mapping, and error handling. Through Jentic: under 30 minutes — search by intent, load the schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Typeform API

Conversational online forms with a richer write API for creating and updating forms, not just reading responses

Choose Typeform when the agent needs to create or edit forms programmatically, or when the use case calls for a conversational one-question-at-a-time response flow

Alternative

Jotform API

Drag-and-drop online form builder with a broader API covering form creation, payments, and PDF generation

Choose Jotform when the agent needs to create forms on the fly, generate PDF receipts from submissions, or work with the larger Jotform template library

Alternative

Wufoo API

Lightweight online form builder API for retrieving forms, fields, entries, and reports

Choose Wufoo when the existing forms already live in Wufoo, or when the agent needs simple read access to form entries with a similar shape to 123FormBuilder

Complementary

HubSpot Marketing Forms API

Pair 123FormBuilder submissions with HubSpot CRM contacts and marketing automation

Use alongside 123FormBuilder when the agent needs to push form responses into HubSpot as contacts or trigger marketing workflows after a submission lands

Complementary

Mailchimp Marketing API

Add 123FormBuilder submissions to Mailchimp audiences for follow-up email campaigns

Use after a 123FormBuilder submission to subscribe the respondent to a Mailchimp list, tag them, and enrol them in an automated email journey

FAQs

Specific to using 123FormBuilder API API through Jentic.

Why is there no official OpenAPI spec for 123FormBuilder API?

123FormBuilder does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call 123FormBuilder API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the 123FormBuilder API use?

The API uses HTTP Bearer authentication with a JWT token obtained from 123FormBuilder. Every request must include an Authorization: Bearer <jwt> header against https://api.123formbuilder.com/v2. When called through Jentic, the JWT is stored in the Jentic vault and injected at execution time, so the raw token never enters the agent's prompt or context.

Can I retrieve form submissions with the 123FormBuilder API?

Yes. Call GET /forms/{formId}/submissions to list responses for a specific form, and GET /forms/{formId}/submissions/{submissionId} to retrieve a single response by ID. Pair these with GET /forms/{formId}/fields to map each value back to its labelled field. The API exposes read access to submissions and a DELETE endpoint for removing them.

Can I create or modify forms with this API?

No. The current 123FormBuilder API surface is read-focused: you can list forms (GET /forms), fetch a single form (GET /forms/{formId}), inspect its fields, and read or delete submissions. Designing forms, editing fields, or publishing changes still happens in the 123FormBuilder web app.

What are the rate limits for the 123FormBuilder API?

The OpenAPI spec does not declare explicit rate limits. 123FormBuilder applies plan-dependent quotas in production, so handle 429 responses with exponential backoff and check your account's plan documentation before running heavy polling workloads. When agents call the API through Jentic, the SDK surfaces 429 responses unchanged so retry logic stays in your control.

How do I delete a submission through Jentic?

Search Jentic for 'delete 123formbuilder submission', load the schema for DELETE /forms/{formId}/submissions/{submissionId}, and execute it with the form ID and submission ID. The Jentic SDK handles the bearer token from the vault, so the agent only supplies the IDs. This is the typical flow for GDPR erasure or removing test data.

How do I use the 123FormBuilder API with an AI agent?

Install the Jentic Python SDK with pip install jentic, then use the async search/load/execute pattern: search for an intent like 'list 123formbuilder submissions', load the resulting operation schema, and execute it with await client.execute(...). Jentic returns matching 123FormBuilder operations with their input schemas so the agent does not need to read the docs to call the right endpoint.