Cantrip API

Name: Cantrip API
Brand: Cantrip API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey6 EndpointsREST

For Agents

Publish posts to Cantrip CMS collections, fetch recent form submissions, and subscribe to webhooks for new form responses. Suited for editorial pipelines and lead routing.

Install Jentic One Beta

Connect the Cantrip API to your agent

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

Publish a new post into a Cantrip collection with title, body, slug, and featured image

List collections that have Zapier post creation enabled to pick a target post type

Retrieve the most recent 100 form submissions filtered by form UUID

GET STARTED

Start building with Cantrip API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Cantrip API, keeping it validated and agent-ready. The Cantrip API is the Zapier integration surface for the Cantrip CMS, exposing endpoints to publish posts into collections, list configured post types, retrieve recent form submissions, and subscribe to webhooks for new submissions. It targets marketing and editorial workflows that need to push content into a Cantrip site or react to inbound form data without using the dashboard. Authentication is a single header key issued from the site's Zapier settings.

Use Cases

Patterns agents use Cantrip API for, with concrete tasks.

★ Automated Editorial Publishing

An editorial team drafts posts in a headless workflow tool and pushes the finalised content into the Cantrip CMS via POST /posts. The integration sends title, body, slug, teaser, author, and featured image so the site renders the post immediately. This removes the manual copy-paste step at the end of the editorial pipeline.

POST /posts with post_type_uuid, title, body, slug, and featured_image_url to publish a post into a Cantrip collection.

Form Submission Lead Routing

Marketing wants new contact-form submissions to land in their CRM and notify sales in Slack. Subscribing a webhook via POST /webhooks delivers form responses as they arrive, while GET /form-submissions provides a fallback for backfilling missed events. Both endpoints scope by form UUID so different forms can route to different downstream systems.

POST /webhooks with formId and hookUrl to subscribe an external endpoint to a specific Cantrip form's submissions.

Backfill Form Submission History

After connecting a new analytics destination, a team needs the last 100 submissions for each form to seed the dataset. GET /form-submissions returns recent submissions sorted newest first, optionally filtered by form_uuid, so the seeder can iterate through forms and load history before the live webhook stream takes over.

GET /form-submissions?form_uuid=<uuid> for each known form and write the returned submissions into the analytics warehouse.

AI Agent Content Publishing

An agent that drafts blog posts uses Jentic to publish the final draft to Cantrip. It searches for the publish operation, loads the createPost schema, picks the right collection from listPostTypes, and submits the post. Credentials stay in the Jentic vault throughout.

Search Jentic for 'publish a post to Cantrip', call listPostTypes to choose a collection, then execute POST /posts with the selected post_type_uuid and content fields.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/posts

Create a post in a Cantrip collection

GET

/post-types

List collections eligible for Zapier post creation

GET

/form-submissions

List recent form submissions, optionally filtered by form UUID

POST

/webhooks

Subscribe a webhook to form submission events

DELETE

/webhooks

Unsubscribe a webhook by id

GET

/me

Validate the API key and return site info

POST

/posts

Create a post in a Cantrip collection

GET

/post-types

List collections eligible for Zapier post creation

GET

/form-submissions

List recent form submissions, optionally filtered by form UUID

POST

/webhooks

Subscribe a webhook to form submission events

DELETE

/webhooks

Unsubscribe a webhook by id

Why Jentic?

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

Credential isolation

The X-Zapier-Key is stored encrypted in the Jentic vault and injected on every Cantrip request. Agents receive scoped access via Jentic's MAXsystem and never see the raw header value.

Intent-based discovery

Agents search Jentic by intent (e.g., 'publish a post' or 'list form submissions') and Jentic returns the matching Cantrip operation with its input schema, so the agent picks the right one of the 6 endpoints without browsing docs.

Time to first call

Direct Cantrip integration: half a day to wire up the Zapier-style endpoints and webhook handling. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Cantrip API through Jentic.

Why is there no official OpenAPI spec for Cantrip API?

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

Cantrip uses an API key passed in the X-Zapier-Key header, issued from the Zapier integration settings on each site. Through Jentic the key is stored encrypted and injected at execution time so it never enters the agent's prompt context.

Can I publish a post to a specific collection with the Cantrip API?

Yes. Call GET /post-types to find the post_type_uuid for the collection you want, then POST /posts with that UUID along with title and body to publish into it.

How do I stream form submissions in real time through Jentic?

Search Jentic for 'subscribe to Cantrip form submissions', load the subscribeWebhook operation, and execute POST /webhooks with formId and hookUrl. New submissions for that form will be POSTed to your URL.

What are the rate limits for the Cantrip API?

Cantrip does not document rate limits in the OpenAPI spec. The form-submissions endpoint caps results at 100 per call, and we recommend implementing client-side backoff on 429 responses.

Can I retrieve historical form submissions?

GET /form-submissions returns the most recent 100 submissions sorted newest first, optionally filtered by form_uuid. For older history beyond 100 items, rely on webhooks going forward and store events in your own system.

Cantrip API

Connect the Cantrip API to your agent

Capabilities

Start building with Cantrip API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs