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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
TicketSpice

TicketSpice Registrants API

The Registrants API from TicketSpice — 4 operation(s) for registrants.

Documentation Provider Profile APIs.io OpenAPI GitHub

TicketSpice Registrants API is one of 10 APIs that TicketSpice publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Registrants. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against a single base URL, https://api.webconnex.com/v2/public.

4 operations 4 paths 3 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.webconnex.com/v2/public
Authentication
API Key
Contact
API Evangelist
License
Proprietary (Webconnex)
Resource Areas
1

Authentication & Security 1

TicketSpice Registrants API declares 1 security scheme for authenticating requests. An API key is passed in the header as apiKey (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — Account API key generated from the TicketSpice/Webconnex dashboard.

Paths & Operations 4

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

Registrants 4
GET
/search/registrants
Search registrants
searchRegistrants 7 params → 200
GET
/search/registrants/{id}
View registrant
getRegistrant 2 params → 200
POST
/registrant/check-in
Check-in registrant
checkInRegistrant 1 param body → 200
POST
/registrant/check-out
Check-out registrant
checkOutRegistrant 1 param body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ListEnvelope (4 properties), Envelope (2 properties), CheckInRequest (1 property). Each schema is shown below with its type and property counts.

ListEnvelope
object
Standard Webconnex response envelope wrapping a page of objects.
4 properties
Envelope
object
Standard Webconnex response envelope wrapping a single object.
2 properties
CheckInRequest
object
Illustrative body for registrant check-in/check-out.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ticketspice-registrants-api-openapi.yml Raw ↑

Other APIs TicketSpice publishes across the network.

TicketSpice Coupons API
AE Profile APIs.io
TicketSpice Customers API
AE Profile APIs.io
TicketSpice Forms API
AE Profile APIs.io
TicketSpice Health API
AE Profile APIs.io
TicketSpice Orders API
AE Profile APIs.io
TicketSpice Subscriptions API
AE Profile APIs.io
TicketSpice Tickets API
AE Profile APIs.io
TicketSpice Transactions API
AE Profile APIs.io
TicketSpice Webhooks API
AE Profile APIs.io
#Registrants
← Back to T APIs
API Details
ID
ticketspice:ticketspice-registrants-api
Base URL
https://api.webconnex.com/v2/public
Docs
https://docs.webconnex.io/api/v2/
Provider
TicketSpice
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ticketspice-registrants-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ticketspice-registrants-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of TicketSpice Registrants 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.