123FormBuilder API

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 your Jentic One instance 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.

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

Yes. Because Jentic One is self-hosted, your own rules decide which 123FormBuilder operations and credentials the agent can use. Since the form id sits in the URL path (/forms/{formId}/...), you can pin the agent to a single form so it only reads that form's fields and submissions through GET /forms/{formId}/fields and GET /forms/{formId}/submissions. You also choose which operations are allowed, so submission deletion via DELETE /forms/{formId}/submissions/{submissionId} stays off unless you add it.