CaptureIQ API

Name: CaptureIQ API
Brand: CaptureIQ API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityForms Surveysbearer2 EndpointsREST

For Agents

Validate a CaptureIQ API key and pull the most recent form submission across the account. Suited for integration health checks and lightweight inbound polling.

Install Jentic One Beta

Connect the CaptureIQ API to your agent

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

Validate that a configured CaptureIQ API key is active and authorised

Retrieve the most recent form submission across the account in a single call

Poll for new inbound submissions in workflow tools without managing webhooks

GET STARTED

Start building with CaptureIQ API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for CaptureIQ API, keeping it validated and agent-ready. CaptureIQ is a forms and submissions platform, and its REST API exposes a small but practical surface: validate a configured API key and retrieve the most recent submission across the account. The spec is currently in beta, so the published surface is intentionally narrow while the platform expands to more form management endpoints. Operations teams use it to verify integrations and to poll for the latest inbound submission inside automation workflows.

Use Cases

Patterns agents use CaptureIQ API for, with concrete tasks.

★ Integration Health Check

Before kicking off a longer automation, a workflow tool calls GET /api/validateApiKey to confirm the configured CaptureIQ token is still valid. The call returns success or an error and acts as a single-shot probe that prevents downstream steps from running with stale credentials.

GET /api/validateApiKey with the configured bearer token and abort the workflow if the response is not 200.

Inbound Submission Polling

Where webhooks are not viable, automations poll GET /ciq/recent-submission/v1 every minute or so to fetch the latest submission and forward it to a CRM, ticketing tool, or analytics warehouse. Because the endpoint returns the most recent submission, the integration deduplicates by submission id on its side.

Every minute, GET /ciq/recent-submission/v1, dedupe by submission id, and forward new entries to the CRM.

Pre-Send Connectivity Probe

Tools that orchestrate a sequence of vendor calls run a quick probe against CaptureIQ before invoking any side-effecting steps. validateApiKey is a low-cost call that surfaces auth or network issues early so the rest of the run can fail fast with a clear cause.

GET /api/validateApiKey at workflow start, log the result, and proceed only if the call succeeds.

AI Agent Submission Triage

An agent that triages inbound form submissions uses CaptureIQ via Jentic to fetch the latest entry and classify it into the right downstream queue. It searches for the recent-submission operation, loads the schema, and executes the call - credentials stay encrypted in your Jentic One instance.

Search Jentic for 'get the latest CaptureIQ submission', load the recentSubmission schema, and execute GET /ciq/recent-submission/v1 in the agent's poll loop.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/api/validateApiKey

Validate that the bearer token is active

GET

/ciq/recent-submission/v1

Retrieve the most recent form submission

GET

/api/validateApiKey

Validate that the bearer token is active

GET

/ciq/recent-submission/v1

Retrieve the most recent form submission

Why Jentic?

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

Credential isolation

Your CaptureIQ bearer JWT is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'validate a CaptureIQ API key' or 'get the latest CaptureIQ submission', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using CaptureIQ API through Jentic.

Why is there no official OpenAPI spec for CaptureIQ API?

CaptureIQ is in beta and publishes a help-site reference but not an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CaptureIQ API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the CaptureIQ API use?

CaptureIQ uses bearer JWT authentication. The token is sent as Authorization: Bearer <token>. Through Jentic the token is stored encrypted in the vault and injected at execution time, so it never enters the agent's prompt context.

Can I retrieve recent submissions with the CaptureIQ API?

Yes. GET /ciq/recent-submission/v1 returns the most recent submission across the account. Dedupe by submission id when polling so the same entry is not processed twice.

How do I check whether my CaptureIQ token is still valid through Jentic?

Search Jentic for 'validate CaptureIQ API key', load the validateApiKey operation, and execute GET /api/validateApiKey. A 200 response means the token is active.

What are the rate limits for the CaptureIQ API?

The OpenAPI spec does not enumerate rate limits while the API is in beta. Treat as low volume - poll the recent-submission endpoint at most once per minute and back off on 429 responses.

Does CaptureIQ support webhooks for new submissions?

The current beta surface only exposes the validate and recent-submission endpoints. Until a webhook is published, polling /ciq/recent-submission/v1 is the supported way to detect new entries.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. The CaptureIQ API exposes only two read operations, so you scope by operation: allow the agent to validate the API key (GET /api/validateApiKey), to fetch the most recent submission (GET /ciq/recent-submission/v1), or just one of them. The agent can do nothing beyond the set you allow, and your bearer token stays with your own instance rather than in the agent's prompt.