canonical: https://jentic.com/apis/crove.app/crove # Crove App Crove API 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. ## For AI agents Configure webhooks, manage Zapier subscriptions, and run authentication and user management on the Crove document automation platform. ## Scope Does not handle template authoring, document rendering, or PDF storage retrieval - use for Crove webhook, Zapier, and user-management operations only. ## Capabilities - 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 - Run the full authentication lifecycle: login, logout, register, verify email, change password - Inspect and update the currently authenticated user via /auth/user ## Use cases ### 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. Example prompt: 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. Example prompt: 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}. Example prompt: Register a new Crove user with the email new.hire@example.com and confirm the account appears in GET /api/users ### 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. Example prompt: Use the Jentic SDK to register a Crove webhook for document generation events and subscribe a Zap to the same event ## Key endpoints | 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 | Login | | POST | /auth/registration | Register a new user | ## Key resources - **Webhooks** — Retrieve, create, and update outbound webhooks via /api/integrations/webhook endpoints - **Zapier Integration** — Manage Zapier API keys, list templates, and subscribe/unsubscribe to template-document-created events - **Users** — List, retrieve, and update users via /api/users endpoints, including /api/users/me - **Authentication** — Login, logout, registration, email verification, and password change/reset under /auth ## Why Jentic - **Setup:** Wiring Crove by hand means encoding its HTTP basic auth username and password, and threading login, registration, webhook, and Zapier subscription calls yourself. Through Jentic you install once, import Crove from the API Directory, store the basic-auth credentials once, and your agent calls it. - **Permission scoping:** Crove identifies webhooks and Zapier subscriptions in the request body rather than the URL path, so limit the agent to the operations it needs, such as creating a webhook or subscribing a Zap to a template-document-created event. You choose the operations it may call, so account-level actions are not included unless you add them. - **Credential handling:** Your Crove basic-auth username and password are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a Crove webhook' or 'subscribe a Zap to a Crove event', and Jentic returns the matching Crove operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **crowd.dev API** — crowd.dev tracks community activity that can be turned into Crove-generated documents - **Crossmint API** — Crossmint mints NFTs whose metadata can include documents generated by Crove - **Cron-job.org API** — cron-job.org schedules recurring HTTP triggers that can fire Crove document generation events ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Crove API? Yes. Because you run Jentic One yourself, your own rules decide which Crove operations and credentials the agent may use, so you can allow just what it needs, such as creating a webhook with POST /api/integrations/webhook/create or subscribing a Zap to the template-document-created event. Crove identifies webhooks and Zapier subscriptions in the request body rather than the URL path, so you scope the agent at the operation level rather than by path prefix. Account-level actions like user management under /api/users or the authentication endpoints stay off limits unless you explicitly add them.