Crove API

Name: Crove API API
Brand: Crove API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationbasic26 EndpointsREST

For Agents

Configure webhooks, manage Zapier subscriptions, and run authentication and user management on the Crove document automation platform.

Quickstart

Get started with Crove API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a Crove webhook for document generation"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Crove API API.

Configure outbound webhooks via /api/integrations/webhook endpoints to react to document events

Manage Zapier API keys including create and test operations under /api/integrations/zapier/api-key

Subscribe and unsubscribe Zapier flows to the template-document-created event

List Crove users and retrieve or update individual user records

GET STARTED

Start building with Crove API API

Explore with Jentic

View OpenAPI Document

Use for: I need to set up a Crove webhook for new documents, Create a new Zapier API key for our Crove account, List all users in our Crove workspace, Subscribe a Zapier flow to the template-document-created event

Not supported: Does not handle template authoring, document rendering, or PDF storage retrieval — use for Crove webhook, Zapier, and user-management operations only.

Jentic publishes the only available OpenAPI document for Crove API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Crove API, keeping it validated and agent-ready. Crove is a document automation platform that lets teams turn templated documents into structured generation workflows. The publicly documented API exposes webhook configuration, Zapier integration plumbing including template subscriptions, user management, and a full authentication surface for login, registration, password change, and email verification. The API uses HTTP Basic auth.

Use Cases

Patterns agents use Crove API API for, with concrete tasks.

★ Document-Generated Webhook Pipeline

Trigger downstream automation whenever Crove generates a document by registering a webhook with POST /api/integrations/webhook/create and pointing it at a service URL. Customer-success ops, contract pipelines, and CRM sync flows all use this so a downstream tool reacts the moment a templated document is ready, rather than polling. Updates to the webhook target are made through /api/integrations/webhook/update.

Create a Crove webhook that POSTs to https://example.com/crove-events when a new document is generated

Zapier-Triggered Template Workflows

Wire Crove into a Zapier workflow by creating a Zapier API key with POST /api/integrations/zapier/api-key/create, listing available templates with GET /api/integrations/zapier/data/templates, and subscribing to the template-document-created event with POST /api/integrations/zapier/subscriptions/template-document-created. Operations teams use this to turn document generation into the trigger for downstream Zaps without writing custom code.

Create a Zapier API key, subscribe to the template-document-created event for template ID 42, and return the subscription ID

User Account Provisioning

Provision new teammates into Crove by calling POST /auth/registration, then surface the new user via GET /api/users/{id} for downstream tools. Workspace admins use this to keep Crove user state in sync with the company's HR or identity system, including responding to role changes via PATCH /api/users/{id}.

AI Agent Document Workflow Setup

An AI agent helps a workspace admin set up a new document automation flow on Crove through Jentic. The agent searches for the crove_create_webhook operation, executes against the admin's vaulted basic-auth credential, and returns a confirmation. This unlocks turning a natural-language request like 'send our CRM a webhook every time a contract is generated' into a working integration.

Use the Jentic SDK to register a Crove webhook for document generation events and subscribe a Zap to the same event

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/integrations/webhook/create

Create a webhook

POST

/api/integrations/webhook/update

Update a webhook

POST

/api/integrations/zapier/api-key/create

Create a Zapier API key

POST

/api/integrations/zapier/subscriptions/template-document-created

Subscribe to template-document-created events

GET

/api/users

List users

POST

/auth/login

POST

/auth/registration

POST

/api/integrations/webhook/create

Create a webhook

POST

/api/integrations/webhook/update

Update a webhook

POST

/api/integrations/zapier/api-key/create

Create a Zapier API key

POST

/api/integrations/zapier/subscriptions/template-document-created

Subscribe to template-document-created events

GET

/api/users

List users

Why though Jentic?

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

Credential isolation

Crove basic-auth credentials are stored encrypted in the Jentic vault. Agents receive a scoped execution token, and Jentic injects the Authorization header at request time so the username and password never enter the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'create a Crove webhook' or 'subscribe a Zap to a Crove event' and Jentic returns the matching Crove operation with its input schema, removing the need to read the Crove docs.

Time to first call

Direct Crove integration: half a day for basic-auth setup and webhook plumbing. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

crowd.dev API

crowd.dev tracks community activity that can be turned into Crove-generated documents

Use crowd.dev to gather community signals and Crove to generate templated reports or outreach documents from those signals.

Complementary

Crossmint API

Crossmint mints NFTs whose metadata can include documents generated by Crove

Pair Crove document generation with Crossmint when minting NFTs that need an attached, dynamically generated certificate.

Complementary

Cron-job.org API

cron-job.org schedules recurring HTTP triggers that can fire Crove document generation events

Use cron-job.org to trigger a recurring Crove generation flow when an agent doesn't host its own scheduler.

FAQs

Specific to using Crove API API through Jentic.

Why is there no official OpenAPI spec for Crove API?

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

The Crove API uses HTTP Basic Authentication. Through Jentic the username and password are stored encrypted in the vault and Jentic injects the Authorization header at request time so the credentials never enter the agent's context.

Can I subscribe a Zapier flow to a Crove event through the API?

Yes. POST /api/integrations/zapier/subscriptions/template-document-created lets you subscribe a Zapier hook to the template-document-created event, and DELETE /api/integrations/zapier/subscriptions/template-document-created/{subscription_id} removes it.

How do I register a webhook through Jentic?

Search Jentic for 'create a Crove webhook', load the operation schema for POST /api/integrations/webhook/create, and execute with the target URL and event filter. Jentic handles the basic-auth header injection.

How many endpoints does the Crove API expose?

Twenty-six endpoints across webhook configuration, Zapier integration plumbing, user management, and the authentication surface (login, logout, register, verify email, change password).

Can I list and update Crove users programmatically?

Yes. GET /api/users lists users, GET /api/users/{id} retrieves one, and PUT or PATCH /api/users/{id} updates a user record. The currently authenticated user is also exposed via /api/users/me and /auth/user.