Eventcinch E-cinch API
48
AI ReadinessFoundational (D+)48/100
Agent-ready OpenAPI document · curated by JenticE CommerceOrder ManagementapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Validate users, subscribe to E-cinch cart events, and list new or recently updated carts via Zapier-style trigger endpoints.
Use for: Validate the current E-cinch api_key, Subscribe to E-cinch new cart events, I want to unsubscribe from cart update notifications, List all new carts created today
Not supported: Does not handle ticket sales, payments, or attendee check-in - use for E-cinch user validation and cart trigger subscriptions only.
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.
Install Jentic One Beta
Connect the E-cinch API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the E-cinch API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feventcinch.com%2Feventcinch" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feventcinch.com%2Feventcinch" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with E-cinch API.
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
Patterns agents use E-cinch API for, with concrete tasks.
★ 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.
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.
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.
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.
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
7 endpoints — jentic publishes the only available openapi specification for e-cinch api, keeping it validated and agent-ready.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
E
E-cinch API
- Foundational (D+)48/100
100
Foundational Compliance59
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
59
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
36%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
29%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using E-cinch API through Jentic.
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.
GET STARTED