canonical: https://jentic.com/apis/eventcinch.com/eventcinch

# Eventcinch E-cinch API

Jentic publishes the only available OpenAPI specification for E-cinch API, keeping it validated and agent-ready. The E-cinch API is the Zapier-oriented integration surface for the E-cinch event management platform. It exposes endpoints to validate users, subscribe and unsubscribe to new-cart and updated-cart triggers, and list new and recently changed cart records. Authentication uses an api_key query parameter, which Zapier (and other automation platforms) provide on each call.

## For AI agents

Validate users, subscribe to E-cinch cart events, and list new or recently updated carts via Zapier-style trigger endpoints.

## Scope

Does not handle ticket sales, payments, or attendee check-in - use for E-cinch user validation and cart trigger subscriptions only.

## Capabilities

- Validate that an api_key is bound to a real E-cinch user before configuring a Zap
- Subscribe to a new-cart trigger so the platform POSTs new cart records to a callback URL
- Unsubscribe from a previously created new-cart trigger
- Subscribe to an update-cart trigger to receive cart change events
- Unsubscribe from an update-cart trigger
- List recently created new carts for backfill or polling integrations
- List fresh (recently updated) carts that have changed since the last poll

## Use cases

### Zapier-style cart automation

Trigger a downstream automation whenever a new cart is created on E-cinch. POST `/zap/newcart` subscribes a callback URL, and E-cinch then POSTs cart payloads to that URL each time a customer creates a cart. This is the same pattern Zapier uses, but it works with any platform that can host a webhook receiver.

Example prompt: POST `/zap/newcart` with the callback URL and api_key, then verify the subscription identifier appears in subsequent payloads.

### Initial cart backfill

Before turning on the streaming subscription, an integration backfills existing carts so the destination system starts in sync. GET `/zap/carts/new` returns the most recent newly created carts, and GET `/zap/carts/fresh` returns the most recently updated carts, which together cover both first-time and edit cases.

Example prompt: GET `/zap/carts/new` and GET `/zap/carts/fresh`, deduplicate by cart ID, and write each entry into the destination system before enabling the live subscription.

### User key validation in onboarding

When a user pastes an E-cinch api_key into a connector setup screen, the connector calls GET `/zap/user` to confirm the key is valid and tied to the right account before saving it. This avoids storing dead credentials and gives the user a clear error message at setup time.

Example prompt: GET `/zap/user`?api_key={key} and confirm a 200 response with a user payload before persisting the key.

### Agent-driven cart processing via Jentic

An AI agent receives a cart payload via the new-cart subscription, looks up customer history, and pushes a follow-up email through a separate channel. Jentic stores the api_key in your Jentic One instance and injects it as the api_key query parameter at execution time, so the agent never sees the raw value.

Example prompt: Search Jentic for 'list E-cinch fresh carts', load the schema for GET `/zap/carts/fresh`, and execute on a 5-minute schedule.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/zap/user` | Validate the api_key and return user info |
| POST | `/zap/newcart` | Subscribe to new-cart events |
| DELETE | `/zap/newcart` | Unsubscribe from new-cart events |
| POST | `/zap/updatecart` | Subscribe to cart-update events |
| DELETE | `/zap/updatecart` | Unsubscribe from cart-update events |
| GET | `/zap/carts/new` | List recently created carts |
| GET | `/zap/carts/fresh` | List recently updated carts |

## Key resources

- **zap** — Zapier-style trigger endpoints for user validation and cart subscriptions

## Why Jentic

- **Setup:** Wiring the E-cinch API by hand means passing the api_key as a query parameter on every call, targeting the eventcinch.com host, and managing the Zapier-style cart trigger subscriptions yourself. Through Jentic you install once, import the E-cinch API from the API Directory, store the api_key once, and your agent calls it.
- **Permission scoping:** E-cinch carries the cart payload in the request body rather than a URL-path resource, so scope the agent to the operations it needs, such as validating a user or subscribing to new cart events. You choose which operations are allowed, so a DELETE on a cart subscription is not included unless you add it.
- **Credential handling:** Your E-cinch api_key is stored once, encrypted, by your own Jentic One instance and injected as the api_key query parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'subscribe to E-cinch new cart events' or 'validate a user', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Zapier NLA API** — Drive E-cinch triggers from a Zapier natural-language action layer
- **Ticketmaster Discovery API** — Ticketmaster offers a different surface for event and ticket data with broader market coverage
- **Cvent API** — Cvent provides enterprise event management with registration and cart-equivalent flows

## FAQ

### Why is there no official OpenAPI spec for E-cinch API?

Eventcinch publishes a Zapier-oriented documentation page rather than a downloadable OpenAPI artefact. Jentic generates and maintains this spec so that AI agents and developers can call E-cinch 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 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.