What authentication does the E-cinch API use?

An api_key query parameter on each request, named exactly api_key. Through Jentic the key is held in your Jentic One instance and injected into the query string so the agent never embeds it in code.

Can I subscribe to cart events without using Zapier?

Yes. POST /zap/newcart and POST /zap/updatecart accept any HTTPS callback URL - they are Zapier-shaped but work with any webhook receiver. The callback URL receives cart payloads as soon as the event fires.

What are the rate limits for the E-cinch API?

Rate limits are not declared in the OpenAPI spec. E-cinch operates the API primarily for Zapier-style polling, so polite intervals (typically 5 minutes or longer) are expected. Contact eventcinch.com support for the specific ceiling on your account.

How do I list new carts through Jentic?

Use the Jentic search query 'list E-cinch new carts', which resolves to GET /zap/carts/new. Run pip install jentic, load the operation, and execute - Jentic appends api_key from the vault automatically.

How do I clean up an old subscription?

Call DELETE /zap/newcart or DELETE /zap/updatecart with the subscription identifier returned at creation time. This stops E-cinch from posting events to the callback URL and prevents orphaned subscriptions from accumulating.

Can I limit what my agent is allowed to do with the E-cinch API?

Yes. Because you run Jentic One yourself, your own rules decide which E-cinch operations and credentials the agent may use, so you can allow just what a task needs, such as GET /zap/user to validate a key or POST /zap/newcart to subscribe to new cart events. Read-only work like GET /zap/carts/new and GET /zap/carts/fresh can be permitted without granting any subscribe or unsubscribe rights. A destructive call such as DELETE /zap/newcart stays off the agent's list unless you add it. The api_key is held by your instance and injected at execution time, so the agent never handles the raw credential.