What events can I subscribe webhooks to?

Three triggers are available: orders/new for newly created orders, orders/status-changed for status transitions, and products/low-stock for products dipping below their threshold. Subscribe by POSTing to /api/zapier/webhooks/subscribe with the event name and target URL.

How do I unsubscribe a webhook I no longer need?

POST /api/zapier/webhooks/unsubscribe with the subscription you want removed. Once unsubscribed, Ordavia stops delivering events to that target URL - useful when retiring a downstream integration without removing the credential.

Why do the paths sit under /api/zapier?

The current REST surface mirrors Ordavia's Zapier integration shape - auth test, triggers, and subscribe/unsubscribe - so consumers can reuse the same trigger semantics outside Zapier. There is no separate non-Zapier path in this version of the spec.

How do I subscribe to new Ordavia orders through Jentic?

Install the SDK with pip install jentic, then search for 'subscribe to new Ordavia orders'. Jentic returns the POST /api/zapier/webhooks/subscribe operation; load it, supply the orders/new event and the target URL, and execute. Run it through Jentic One, the self-hosted execution layer.

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

Yes. Because you run Jentic One yourself, your own rules decide which Ordavia operations and credentials the agent may use, so you choose exactly which of the six endpoints it can call. You might allow only read operations such as the auth test, the new-order trigger, the status-changed trigger, and the low-stock trigger, while keeping the webhook subscribe and unsubscribe operations out of the allowed set unless you explicitly add them. Your Ordavia bearer token is injected at execution time and never enters the agent's prompt or context.