For Agents
List NeetoForm forms, fetch form submissions, and manage workspace team members through a workspace-scoped API.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NeetoForm 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 NeetoForm API.
List all forms in a NeetoForm workspace via GET /forms
Page through submissions for a specific form via GET /forms/{form_id}/submissions
List current team members of the workspace via GET /team_members
GET STARTED
Use for: I need to list all forms in my NeetoForm workspace, Fetch the most recent submissions for a specific form, Add a new team member to the NeetoForm workspace, Update a team member's role in NeetoForm
Not supported: Does not create forms, send transactional email, or process payments — use for read-only form access and team-member management only.
Jentic publishes the only available OpenAPI specification for NeetoForm API, keeping it validated and agent-ready. The NeetoForm API exposes 6 endpoints for managing forms, submissions, and team members in a NeetoForm workspace. It supports listing forms, paging through form submissions, and adding, updating, or removing team members. Authentication uses an X-Api-Key header issued from the NeetoForm dashboard, and the base URL is workspace-scoped via the {subdomain} parameter on neetoform.com.
Add new team members in bulk via POST /team_members
Update an existing team member's role via PATCH /team_members/{team_member_id}
Remove team members in bulk via DELETE /team_members
Patterns agents use NeetoForm API for, with concrete tasks.
★ Sync Form Submissions to a CRM
An ops team syncs NeetoForm submissions into a downstream CRM by polling /forms/{form_id}/submissions on a schedule, transforming each submission into a contact record, and stopping when the cursor reaches the previously synced submission id. The 6-endpoint surface keeps the integration thin, and the X-Api-Key keeps the sync scoped to the issuing workspace.
GET /forms/{form_id}/submissions with the latest cursor and POST each new submission as a contact in the downstream CRM.
Workspace Team Management Automation
An admin automates onboarding by adding new hires to the NeetoForm workspace as form editors when they join, then revoking access when they leave. The /team_members endpoints support bulk add and bulk delete, and PATCH /team_members/{team_member_id} updates roles when someone changes teams internally.
POST /team_members with the new hire's email and role, then PATCH /team_members/{team_member_id} when the role changes.
Form Inventory Audit
A compliance team audits which forms exist across the workspace and how many submissions each has gathered, by listing /forms and then iterating /forms/{form_id}/submissions for each. The audit produces a record of every active intake form, its submission volume, and the last submission timestamp.
GET /forms, then for each form id GET /forms/{form_id}/submissions?limit=1 to record the latest submission timestamp.
Agent-Driven Form Operations
An AI assistant inside a workspace tool uses Jentic to fetch the most recent NeetoForm submissions in response to a chat query, without hard-coding the X-Api-Key header or pagination logic. The agent searches for the right operation, loads the schema, and submits the call while Jentic manages the API key.
Search Jentic for 'list NeetoForm submissions for a form', load the schema for GET /forms/{form_id}/submissions, and execute it with the form id.
6 endpoints — jentic publishes the only available openapi specification for neetoform api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/forms
List forms in the workspace
/forms/{form_id}/submissions
List submissions for a form
/team_members
List team members
/team_members
Add team members
/team_members/{team_member_id}
Update a team member
/team_members
Remove team members
/forms
List forms in the workspace
/forms/{form_id}/submissions
List submissions for a form
/team_members
List team members
/team_members
Add team members
/team_members/{team_member_id}
Update a team member
Three things that make agents converge on Jentic-routed access.
Credential isolation
NeetoForm X-Api-Key values are stored encrypted in the Jentic vault and tied to the issuing workspace subdomain. Agents receive a scoped session at execution time so the raw API key never enters agent context.
Intent-based discovery
Agents search by intent such as 'list NeetoForm submissions for a form' and Jentic returns the matching operation with its input schema, removing the need to read the NeetoForm docs.
Time to first call
Direct NeetoForm integration: a couple of hours for auth, pagination, and the team-member endpoints. Through Jentic: minutes to fetch submissions or rotate team members with managed credentials.
Alternatives and complements available in the Jentic catalogue.
Specific to using NeetoForm API through Jentic.
Why is there no official OpenAPI spec for NeetoForm API?
NeetoForm publishes its external API as developer documentation rather than a formal OpenAPI file. Jentic generates and maintains this spec so that AI agents and developers can call NeetoForm API via structured tooling. It is validated against the live neetoform.com endpoints and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the NeetoForm API use?
NeetoForm uses an apiKey scheme with the X-Api-Key header. Generate the key from the NeetoForm workspace settings and send it on every request to {subdomain}.neetoform.com/api/external/v1. Through Jentic the key is stored encrypted in the vault and injected at execution time.
Can I retrieve form submissions with the NeetoForm API?
Yes. GET /forms/{form_id}/submissions returns the submissions for that form, paginated. Use the response cursor to walk through older submissions when syncing to a downstream system.
What are the rate limits for the NeetoForm API?
NeetoForm does not publish numeric per-endpoint rate limits in the OpenAPI document; the workspace plan governs throughput. Treat sustained polling above a few requests per second as risky on smaller plans and back off on 429 responses.
How do I add a team member through Jentic?
Run pip install jentic, then search for 'add a NeetoForm team member', load the schema for POST /team_members, and execute it with the new member's email and role. Jentic returns the created team member record.
Does the NeetoForm API let me create forms?
No. The external v1 surface only exposes listing forms, reading their submissions, and managing team members. Form creation and design happen inside the NeetoForm dashboard.
/team_members
Remove team members