What authentication does the KitchenHub API use?

KitchenHub uses Bearer token authentication. Tokens are issued by POST /v2/auth/token/ and refreshed by POST /v2/auth/token/refresh/. Jentic stores the long-lived credentials in the vault and manages the token lifecycle internally.

Can I subscribe to order events with the KitchenHub API?

Yes. Call POST /v2/webhooks/ with a destination URL and the event types you want to receive. Use PATCH /v2/webhooks/{webhook_id}/ to adjust filters and DELETE /v2/webhooks/{webhook_id}/ to remove the subscription.

What are the rate limits for the KitchenHub API?

The OpenAPI specification does not declare explicit rate limits across the 48 endpoints. Validate the access token with GET /v2/auth/token/validate/ rather than refreshing on every request, and back off if the API returns a 429.

How do I create a KitchenHub location through Jentic?

Run pip install jentic, search Jentic for 'create a KitchenHub location', load the POST /v2/locations/ operation, and execute it with the site address. Jentic handles the Bearer token issuance and refresh cycle automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which KitchenHub operations and credentials the agent can use, so you scope access per operation. For example, you can allow the agent to create stores with POST /v2/stores/ or read providers with GET /v2/providers/ while leaving webhook changes like PATCH /v2/webhooks/{webhook_id}/ out unless you explicitly add them. Since KitchenHub carries location, store, and integration targets in the request body and only pins a resource in the path for webhook updates, limiting the operation set is what controls what the agent can reach. Your KitchenHub credential stays with your instance and is injected only when a permitted operation runs.