Crewform Tech CrewForm API

Name: CrewForm API
Brand: CrewForm API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLLanguage ModelsapiKey, bearer18 EndpointsREST

For Agents

Manage CrewForm agents, tasks, teams, and team runs from outside the CrewForm UI, and subscribe webhooks to react to platform events. Use it to drive multi-agent workflows from your own backend or another agent.

Install Jentic One Beta

Connect the CrewForm API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CrewForm 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcrewform.tech%2Fcrewform" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcrewform.tech%2Fcrewform" | 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 CrewForm API.

List, create, update, and delete CrewForm agents through the /api-agents endpoint

Queue work with /api-tasks, optionally auto-dispatching when an agent or team is assigned

Organise agents into teams and update team membership through /api-teams

GET STARTED

Start building with CrewForm API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CrewForm API for, with concrete tasks.

★ External backend driving multi-agent workflows

Drive CrewForm from an external service rather than its UI by creating agents, assigning them to teams, and starting team runs whenever a business event occurs. The /api-runs endpoint accepts the team and inputs in one POST and returns a run record, so the backend can fire-and-forget a workflow and inspect the result later.

Call POST /api-runs with the target team's ID and an inputs object describing the new lead, then poll GET /api-runs to find the matching run and read its status.

Task queue for autonomous agents

Use CrewForm tasks as a managed work queue: an external system creates a task with POST /api-tasks naming the agent or team and the task is auto-dispatched. This is useful when one product wants to delegate a job to a CrewForm agent without orchestrating LLM calls itself.

Call POST /api-tasks with title, description, and assigned_agent_id; CrewForm auto-dispatches and the response includes the dispatched task ID for follow-up.

Webhook-driven downstream automation

Wire CrewForm into Zapier or another REST Hook consumer by subscribing webhooks via POST /api-hooks. When a team run completes or a task changes state, the subscribed URL receives the payload, so downstream systems like CRMs, Slack, or ticketing tools update without polling.

Call POST /api-hooks with the target_url and event filter for run.completed, then DELETE /api-hooks to remove the subscription when no longer needed.

Agent-to-agent delegation through Jentic

Let a Jentic-managed agent delegate work to a CrewForm team without hard-coding endpoints by searching Jentic for a 'start a team run' operation. Jentic returns POST /api-runs with its schema, the agent fills in team_id and inputs, and Jentic injects the X-API-Key from the vault.

Through Jentic, run search('start a CrewForm team run'), load POST /api-runs, and execute it with the chosen team_id and the user's brief as inputs.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api-agents

Create an agent

POST

/api-tasks

Create a task and auto-dispatch when assigned

POST

/api-teams

Create a team

POST

/api-runs

Start a new team run

GET

/api-runs

List team runs

POST

/api-hooks

Subscribe a Zapier REST Hook

GET

/api-me

Get current user identity

POST

/api-agents

Create an agent

POST

/api-tasks

Create a task and auto-dispatch when assigned

POST

/api-teams

Create a team

POST

/api-runs

Start a new team run

GET

/api-runs

List team runs

POST

/api-hooks

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring CrewForm by hand means pointing at your Supabase project host, choosing between the cf_ API key and a JWT bearer, and sending each header on the right call. Through Jentic you install once, import CrewForm from the API Directory, store the key once, and your agent calls it.

Permission scoping

CrewForm creates agents, tasks, teams, and runs through collection paths and the request body rather than URL resource ids, so scope the agent to the operations it needs, such as creating an agent or starting a run. Creating webhooks stays out unless you include that operation.

Credential isolation

Your CrewForm cf_ key is stored once, encrypted, by your own Jentic One instance and applied as the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'start a CrewForm team run' or 'create an agent in CrewForm', and Jentic returns the matching CrewForm operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using CrewForm API through Jentic.

Why is there no official OpenAPI spec for CrewForm API?

CrewForm publishes API reference docs at docs.crewform.tech but does not ship an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CrewForm 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 CrewForm API use?

The API supports two schemes: an X-API-Key header carrying a key prefixed with cf_ created in Settings -> API Keys, and bearer JWTs for authenticated frontend clients. Server-side integrations should use the X-API-Key header; through Jentic the key is stored encrypted and applied at execution time.

Can I auto-dispatch a task to a CrewForm agent through the API?

Yes. POST /api-tasks creates a task and auto-dispatches it when the request body assigns an agent or team, so the calling system does not need a separate dispatch step.

How do I subscribe a webhook to CrewForm events?

POST /api-hooks with the target URL to register a Zapier-style REST Hook subscription for events such as run completion. List active subscriptions with GET /api-hooks and remove one with DELETE /api-hooks when it is no longer needed.

What are the rate limits for the CrewForm API?

CrewForm enforces rate limits on its Edge Functions surface. The OpenAPI spec mentions rate limiting in the description but does not declare numeric ceilings, so check the response headers and your plan in the CrewForm dashboard. Build retries with backoff around HTTP 429 on POST /api-tasks and POST /api-runs.

How do I start a CrewForm team run from a Jentic agent?

Install Jentic with pip install jentic, then async-search for 'start a CrewForm team run'. Load POST /api-runs and execute it with the target team_id and an inputs object. Jentic attaches the X-API-Key from the vault and returns the new run record.

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

Yes. Because you run Jentic One yourself, your own rules decide which CrewForm operations and credentials the agent can use. Since CrewForm acts on agents, tasks, teams, and runs through collection paths and the request body rather than per-resource URLs, you can allow only the operations the agent needs, such as creating an agent with POST /api-agents or starting a team run with POST /api-runs. Subscribing webhooks through POST /api-hooks stays out of reach unless you explicitly include that operation.

Crewform Tech CrewForm API

Connect the CrewForm API to your agent

Capabilities

Start building with CrewForm API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs