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

vivenu ticket-transfers API

The ticket-transfers API from vivenu — 6 operation(s) for ticket-transfers.

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

Tagged areas include ticket-transfers. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 6 paths, and defines 7 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.

7 operations 6 paths 7 schemas 4 GET3 POST

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
Resource Areas
1

Authentication & Security 4

vivenu ticket-transfers 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 7

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

ticket-transfers 7
GET
/api/ticket-transfers
Get All Ticket Transfers
get_all_ticket_transfers 9 params → 200400401
POST
/api/ticket-transfers
Create Ticket Transfer
create_ticket_transfer body → 200400401404
GET
/api/public/ticket-transfers
Get Public Ticket Transfers
get_public_ticket_transfers 6 params → 200400401404
GET
/api/ticket-transfers/{id}
Get a Ticket Transfer
get_a_ticket_transfer 1 param → 200400401404
GET
/api/ticket-transfers/{id}/{secret}
Get Public Ticket Transfer
get_public_ticket_transfer 2 params → 200400404
POST
/api/ticket-transfers/{id}/reject
Reject Ticket Transfer
reject_ticket_transfer 1 param body → 200400401404
POST
/api/ticket-transfers/{id}/accept
Accept Ticket Transfer
accept_ticket_transfer 1 param body → 200400401404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are TicketTransferResource (15 properties), PublicTicketTransferResource (10 properties), POST_Ticket-transfers_CreateTicketTransfer (4 properties), POST_Ticket-transfers_AcceptTicketTransfer (4 properties). Each schema is shown below with its type and property counts.

POST_Ticket-transfers_RejectTicketTransfer
object
1 property 1 required
GET_Ticket-transfers_GetPublicTicketTransfers_200_response
array
TicketTransferResource
object
The associated ticket transfer which has been expired
15 properties 9 required
PublicTicketTransferResource
object
10 properties 5 required
POST_Ticket-transfers_AcceptTicketTransfer
object
4 properties 3 required
POST_Ticket-transfers_CreateTicketTransfer
object
4 properties 2 required
GET_Ticket-transfers_GetAllTicketTransfers_200_response
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vivenu-ticket-transfers-api-openapi.yml Raw ↑

Other APIs vivenu publishes across the network.

vivenu access-lists API
vivenu accessusers API
vivenu api API
vivenu api_keys API
vivenu attributes API
vivenu auth API
vivenu billing API
vivenu bundles API
vivenu cancellations API
vivenu channels API
vivenu chargebacks API
vivenu checkout API
Where this information came from

This is an independent, third-party profile of vivenu ticket-transfers 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.