Crove App Crove API

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.