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
vivenu

vivenu tickets API

The tickets API from vivenu — 22 operation(s) for tickets.

Documentation Provider Profile APIs.io OpenAPI GitHub

vivenu tickets API is one of 73 APIs that vivenu publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tickets. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 23 operations across 22 paths, and defines 18 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://vivenu.com, https://vivenu.dev.

23 operations 22 paths 18 schemas 7 GET15 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://vivenu.com/api
Authentication
HTTP Bearer, API Key, HTTP Bearer, API Key
Contact
vivenu GmbH
Resource Areas
1

Authentication & Security 4

vivenu tickets API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwt). An API key is passed in the header as Authorization (apikey). It accepts HTTP bearer tokens (JWT) (customer-jwt). An API key is passed in the header as Authorization (orgApiKey).

Paths & Operations 23

Across 22 paths, the API surfaces 23 operations — 7 GET, 15 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

tickets 23
GET
/api/tickets
Get all Tickets
tickets/list 24 params → 200400401
GET
/api/tickets/{id}
Get a Ticket
tickets/get 1 param → 200400401404
PUT
/api/tickets/{id}
Update a Ticket
tickets/update 1 param body → 200400401404
GET
/api/tickets/batch/{batchId}
Get Tickets of Batch
tickets/getBatch 2 params → 200400404
GET
/api/tickets/{id}/{secret}
Get Ticket information
tickets/getPublic 4 params → 200400404
GET
/api/public/tickets/upgrades/info
Get ticket upgrade info
tickets/upgradeInfo 2 params → 200400
GET
/api/public/tickets/{id}/return-info
Return a Ticket
tickets/getReturnInfo 3 params → 200400
GET
/api/tickets/{id}/print/{secret}
Get Ticket Print Data
get_ticket_print_data 5 params → 200400404
POST
/api/tickets/free
Create free Tickets
tickets/create body → 201400401
POST
/api/public/tickets/claim
Claim tickets
tickets/claim body → 200400401
POST
/api/public/tickets/upgrade
Upgrade tickets
tickets/upgrade body → 200400401
POST
/api/tickets/{id}/reissue
Reissue Ticket
tickets/reissue 1 param → 200401
POST
/api/tickets/{id}/invalidate
Invalidate Ticket
tickets/invalidate 2 params → 200400401
POST
/api/tickets/{id}/mail
Send Ticket per mail
send_ticket_per_mail 1 param body → 200400401
POST
/api/tickets/{id}/seat
Change Ticket's seat
change_tickets_seat 1 param body → 200400401
POST
/api/tickets/{id}/validate
Validate Ticket
tickets/validate 1 param → 200401
POST
/api/tickets/{id}/detailsrequired
Require Details
tickets/requireDetails 1 param → 200401
POST
/api/tickets/{id}/preparedelivery
Prepare Ticket for delivery
prepare_ticket_for_delivery 1 param → 200401
POST
/api/public/tickets/{id}/return
Return a Ticket
tickets/return 1 param body → 200400
POST
/api/public/tickets/{id}/invalidate
Invalidate Ticket
tickets/invalidatePublic 3 params → 200400
POST
/api/tickets/batch/{id}/invalidate
Invalidate Tickets of a Batch
tickets/invalidateBatch 1 param → 201401
POST
/api/tickets/batch/{id}/mail
Send batch tickets per mail
send_batch_tickets_per_mail 1 param body → 200400401
POST
/api/tickets/personalize/{id}/{secret}
Personalize a Ticket
tickets/personalize 2 params body → 200400401

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are TicketResource (60 properties), CheckoutResource (29 properties), CustomerResource (23 properties), GET_Tickets_GetTicketPrintData_200_response (12 properties). Each schema is shown below with its type and property counts.

POST_Tickets_SendBatchTicketsPerMail
object
1 property 1 required
POST_Tickets_PersonalizeATicket
object
4 properties
POST_Tickets_InvalidateTicketsOfABatch_201_response
array
CustomerResource
object
The associated customer which has been updated
23 properties 2 required
CreateFreeTicketValidationSchema
POST_Tickets_ChangeTicketsSeat
object
4 properties 1 required
TicketResource
object
The associated ticket which has been updated
60 properties 10 required
GET_Tickets_GetAllTickets_200_response
object
2 properties
POST_Tickets_CreateFreeTickets_201_response
array
POST_Tickets_UpgradeTickets
object
3 properties 1 required
CheckoutResource
object
The associated checkout
29 properties 7 required
POST_Tickets_ClaimTickets
object
1 property
GET_Tickets_GetTicketsOfBatch_200_response
array
LegalIdentificationDocumentResource
POST_Tickets_ReturnATicket
object
2 properties 2 required
POST_Tickets_SendTicketPerMail
object
1 property 1 required
PUT_Tickets_UpdateATicket
object
3 properties
GET_Tickets_GetTicketPrintData_200_response
object
12 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vivenu-tickets-api-openapi.yml Raw ↑

Other APIs vivenu publishes across the network.

vivenu access-lists API
AE Profile APIs.io
vivenu accessusers API
AE Profile APIs.io
vivenu api API
AE Profile APIs.io
vivenu api_keys API
AE Profile APIs.io
vivenu attributes API
AE Profile APIs.io
vivenu auth API
AE Profile APIs.io
vivenu billing API
AE Profile APIs.io
vivenu bundles API
AE Profile APIs.io
vivenu cancellations API
AE Profile APIs.io
vivenu channels API
AE Profile APIs.io
vivenu chargebacks API
AE Profile APIs.io
vivenu checkout API
AE Profile APIs.io
#Tickets
← Back to V APIs
API Details
ID
vivenu:vivenu-tickets-api
Base URL
https://vivenu.com/api
Docs
https://vivenu.com/developers
Provider
vivenu
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=vivenu-tickets-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/vivenu-tickets-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 vivenu tickets 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.