MokaForm

Name: MokaForm API
Brand: MokaForm
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityForms Surveysbearer17 EndpointsREST

For Agents

Manage MokaForm API keys, retrieve questionnaire definitions and submissions, configure Stripe payment accounts, and subscribe webhooks to form events.

Install Jentic One Beta

Connect the MokaForm to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MokaForm, 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 | sh

Step 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 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 MokaForm API.

Issue and rotate scoped API keys for MokaForm integrations

Retrieve questionnaire definitions and sample submission payloads

Subscribe webhook URLs to questionnaire events for downstream automation

Configure Stripe Connect accounts on a MokaForm organisation for payment forms

GET STARTED

Start building with MokaForm API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for MokaForm, keeping it validated and agent-ready. MokaForm is a form and questionnaire platform that supports automated submission collection, Stripe-based payment forms, themed surveys, and outbound webhooks for Zapier integrations. The API exposes endpoints to manage scoped API keys, retrieve questionnaire definitions and sample submissions, configure organisation-level Stripe accounts for payment forms, and subscribe webhooks to questionnaire events. It targets product teams embedding self-serve forms with payment capture into their flows.

Use Cases

Patterns agents use MokaForm API for, with concrete tasks.

★ Stripe-Powered Payment Form Onboarding

Onboard an organisation to MokaForm's payment-form feature by creating a connected Stripe account and exposing the dashboard link. The Stripe account endpoints handle the Connect onboarding flow so users can collect payments through MokaForm questionnaires without leaving the platform. Suitable for SaaS teams embedding MokaForm into a multi-tenant workflow where each tenant takes payments separately.

Call GET /organizations/{organizationId}/payment/stripe/create-account to start onboarding, then GET /organizations/{organizationId}/payment/stripe/dashboard/{accountId} to retrieve the dashboard link.

Webhook-Driven Submission Automation

Subscribe a Zapier webhook to a MokaForm questionnaire so that every new submission triggers downstream automation in CRM, email, or analytics tools. The webhook endpoints accept a target URL and return a webhook ID for later removal, replacing manual export-import flows with real-time event delivery. Useful for ops teams stitching MokaForm into a wider Zapier or n8n-driven workflow.

Call POST /webhook/zapier/subscribe with the target URL and questionnaire ID to register a new webhook, then DELETE /webhook/zapier/{webhookId} to unsubscribe later.

Programmatic Questionnaire Schema Discovery

Retrieve a sample submission and the questionnaire's submission definition before mapping form responses to internal data models. The sample and definition endpoints together describe both the field shape and a representative payload, which is how integrations avoid building per-questionnaire mapping by trial and error. Helpful for engineering teams building one-off MokaForm-to-database loaders.

Call GET /questionnaires/{questionnaireId}/submissions/sample/definition to get the field schema, then GET /questionnaires/{questionnaireId}/submissions/sample for a representative payload.

Agent-Driven Form Operations

AI agents managing MokaForm operations call the API through Jentic to rotate API keys, list automation-eligible questionnaires, and subscribe webhooks without holding the bearer token in their context. Jentic's spec is the only structured definition for MokaForm, so schema-aware agents rely on it for tool selection and parameter validation.

Search Jentic for 'subscribe a webhook to a form', load POST /webhook/zapier/subscribe, and execute with the target URL.

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for mokaform, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api-keys

Create a new MokaForm API key

GET

/api-keys

List existing API keys

GET

/automation/questionnaires

List questionnaires eligible for automation

GET

/questionnaires/{questionnaireId}/submissions/sample

Retrieve a sample submission for a questionnaire

GET

/questionnaires/{questionnaireId}/submissions/sample/definition

Retrieve the submission schema definition

POST

/webhook/zapier/subscribe

Subscribe a webhook to questionnaire events

DELETE

/webhook/zapier/{webhookId}

Unsubscribe a webhook

GET

/organizations/{organizationId}/payment/stripe/create-account

Start Stripe Connect onboarding for an organisation

POST

/api-keys

Create a new MokaForm API key

GET

/api-keys

List existing API keys

GET

/automation/questionnaires

List questionnaires eligible for automation

GET

/questionnaires/{questionnaireId}/submissions/sample

Retrieve a sample submission for a questionnaire

GET

/questionnaires/{questionnaireId}/submissions/sample/definition

Retrieve the submission schema definition

Why Jentic?

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

Credential isolation

MokaForm bearer tokens are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. Agents never see the raw token.

Intent-based discovery

Agents search by intent (e.g., 'subscribe a webhook to a form') and Jentic returns the matching MokaForm operation with its parameter schema.

Time to first call

Direct integration: 1-2 days to wire up bearer auth, webhook subscription, and Stripe Connect onboarding. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using MokaForm API through Jentic.

Why is there no official OpenAPI spec for MokaForm?

MokaForm does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MokaForm 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 MokaForm API use?

MokaForm uses HTTP Bearer authentication. Generate a key through POST /api-keys, then send it as Authorization: Bearer <token>. Through Jentic, the bearer token is stored encrypted in the credential vault and injected at request time so the secret never appears in agent context.

Can I capture payments through MokaForm?

Yes. Connect a Stripe account to a MokaForm organisation via GET /organizations/{organizationId}/payment/stripe/create-account, then list connected accounts with GET /organizations/{organizationId}/payment/stripe/accounts. Once the account is live, MokaForm questionnaires can collect payments routed to that connected Stripe account.

What are the rate limits for the MokaForm API?

MokaForm does not publish formal rate limits in this OpenAPI spec. Check https://mokaform.com or your account documentation for current limits. As with most form platforms, expect tighter limits on submission ingestion endpoints than on read-only schema endpoints.

How do I subscribe a webhook through Jentic?

Run pip install jentic, search for 'subscribe a webhook to a form', load POST /webhook/zapier/subscribe, and execute with the questionnaire ID and target URL. Jentic returns the webhook ID, which you keep for later use with DELETE /webhook/zapier/{webhookId}.

Can I retrieve the schema of a MokaForm questionnaire?

Yes. GET /questionnaires/{questionnaireId}/submissions/sample/definition returns the structured definition of the submission shape, and GET /questionnaires/{questionnaireId}/submissions/sample returns a representative payload. Together they let an integration map MokaForm responses without manual inspection.

MokaForm

Connect the MokaForm to your agent

Capabilities

Start building with MokaForm API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs