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 third API

The third API from vivenu — 7 operation(s) for third.

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

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

This API exposes 7 operations across 7 paths, and defines 10 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 7 paths 10 schemas 3 GET4 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 third 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 7 paths, the API surfaces 7 operations — 3 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

third 7
GET
/api/third/exchange/validate
Validate a ticket by its barcode
validate_a_ticket_by_its_barcode 3 params → 200400
GET
/api/third/exchange/validate/tickets
Receive the ticket exchange payload for multiple tickets
receive_the_ticket_exchange_payload_for_multiple_tickets 2 params → 200400
GET
/api/third/exchange/listings/{id}/validate
Validates the active listing for multiple tickets
validates_the_active_listing_for_multiple_tickets 1 param → 200400
POST
/api/third/exchange/listings
Notifies the system that a ticket has been listed on a third party platform
notifies_the_system_that_a_ticket_has_been_listed_on_a_third_party_platform body → 200400
POST
/api/third/exchange/swap
Swap a ticket with barcode and new customer information
swap_a_ticket_with_barcode_and_new_customer_information body → 200400
POST
/api/third/exchange/swap/tickets
Swap multiple tickets with new customer information
swap_multiple_tickets_with_new_customer_information body → 200400
POST
/api/third/exchange/listings/{id}/cancel
Notifies the system that a listings has been canceled on a third party platform
notifies_the_system_that_a_listings_has_been_canceled_on_a_third_party_platform 1 param → 200400

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are POST_Third_SwapATicketWithBarcodeAndNewCustomerInformation_200_response (7 properties), GET_Third_ValidateATicketByItsBarcode_200_response (7 properties), POST_Third_SwapMultipleTicketsWithNewCustomerInformation (4 properties), GET_Third_ReceiveTheTicketExchangePayloadForMultipleTickets_200_response (3 properties). Each schema is shown below with its type and property counts.

GET_Third_ReceiveTheTicketExchangePayloadForMultipleTickets_200_response
object
3 properties 1 required
POST_Third_SwapMultipleTicketsWithNewCustomerInformation
object
4 properties 3 required
GET_Third_ValidatesTheActiveListingForMultipleTickets_200_response
object
3 properties 1 required
POST_Third_SwapATicketWithBarcodeAndNewCustomerInformation
object
2 properties 1 required
POST_Third_SwapATicketWithBarcodeAndNewCustomerInformation_200_response
object
7 properties 5 required
POST_Third_SwapMultipleTicketsWithNewCustomerInformation_200_response
array
POST_Third_NotifiesTheSystemThatAListingsHasBeenCanceledOnAThirdPartyPlatform_200_response
object
GET_Third_ValidateATicketByItsBarcode_200_response
object
7 properties 5 required
POST_Third_NotifiesTheSystemThatATicketHasBeenListedOnAThirdPartyPlatform
object
2 properties 2 required
POST_Third_NotifiesTheSystemThatATicketHasBeenListedOnAThirdPartyPlatform_200_response
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vivenu-third-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 third 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.