How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Eventzilla Checkout API

Checkout workflow operations

Eventzilla Checkout API is one of 7 APIs that Eventzilla publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Checkout. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 4 operations across 4 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://www.eventzillaapi.net/api/v2.

4 operations 4 paths 16 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://www.eventzillaapi.net/api/v2/
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Eventzilla Checkout API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Checkout 4

Checkout workflow operations

GET
/checkout/prepare/{eventid}/{dateid}
Prepare checkout session
prepareCheckout 2 params → 200
POST
/checkout/create
Create checkout
createCheckout body → 200
POST
/checkout/fillorder
Fill order details
fillOrder body → 200
POST
/checkout/confirm
Confirm checkout
confirmCheckout body → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are CheckoutConfirmResponse (9 properties), TicketTypeOption (8 properties), CheckoutFillOrderResponse (8 properties), CheckoutCreateResponse (8 properties). Each schema is shown below with its type and property counts.

TicketSelection
object
2 properties
TicketFillItem
object
5 properties
TicketTypeOption
object
8 properties
PaymentOption
object
2 properties
Question
object
7 properties
Tax
object
3 properties
BuyerDetails
object
3 properties
CheckoutCreateResponse
object
8 properties
CheckoutTicket
object
3 properties
CheckoutConfirmResponse
object
9 properties
CheckoutCreateRequest
object
4 properties 3 required
CheckoutConfirmRequest
object
6 properties 4 required
AnswerItem
object
2 properties
CheckoutFillOrderRequest
object
6 properties 6 required
CheckoutFillOrderResponse
object
8 properties
CheckoutPrepareResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eventzilla-checkout-api-openapi.yml Raw ↑

Other APIs Eventzilla publishes across the network.

Eventzilla Attendees API
Eventzilla Categories API
Eventzilla Events API
Eventzilla Tickets API
Eventzilla Transactions API
Eventzilla Users API
Where this information came from

This is an independent, third-party profile of Eventzilla Checkout API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.