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

The accessusers API from vivenu — 10 operation(s) for accessusers.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

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

12 operations 10 paths 13 schemas 1 DELETE7 GET3 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 accessusers 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 12

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

accessusers 12
GET
/api/accessusers
Get all Access Users
accessusers/list → 200401
POST
/api/accessusers
Create an Access User
accessusers/create body → 201400401
GET
/api/accessusers/events
Get all accessible Events
get_all_accessible_events 2 params → 200400
GET
/api/accessusers/me
Get associated AccessUser info
get_associated_access_user_info 1 param → 200404
GET
/api/accessusers/seller
Get associated Seller Id
get_associated_seller_id 1 param → 200404
GET
/api/accessusers/tickets/{barcode}
Get Ticket with barcode
get_ticket_with_barcode 3 params → 200400404
GET
/api/accessusers/{eventId}/tickets
Get Tickets for an Event
get_tickets_for_an_event 6 params → 200400
GET
/api/accessusers/tickets/v2/{eventId}
Get Tickets for an Event v2
get_tickets_for_an_event_v_2 6 params → 200400
POST
/api/accessusers/scans/{eventId}
Create scans
create_scans 2 params body → 200400
POST
/api/accessusers/tickets/{barcode}/scan
Scan Ticket with barcode
scan_ticket_with_barcode 2 params → 200400404
PUT
/api/accessusers/{id}
Update an Access User
accessusers/update 1 param body → 200400401404
DELETE
/api/accessusers/{id}
Delete an Access User
accessusers/delete 1 param → 200400401404

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are AccessUserResource (15 properties), GET_Accessusers_GetTicketWithBarcode_200_response (13 properties), PUT_Accessusers_UpdateAnAccessUser (8 properties), AccessUserInfoResource (5 properties). Each schema is shown below with its type and property counts.

GET_Accessusers_GetAllAccessibleEvents_200_response
array
An array of all events the access user has access to.
GET_Accessusers_GetAssociatedSellerId_200_response
object
1 property 1 required
POST_Accessusers_ScanTicketWithBarcode_200_response
object
2 properties
POST_Accessusers_CreateScans_200_response
object
1 property
PUT_Accessusers_UpdateAnAccessUser
object
8 properties 2 required
GET_Accessusers_GetTicketsForAnEventV2_200_response
object
2 properties
AccessUserResource
object
15 properties 6 required
GET_Accessusers_GetTicketWithBarcode_200_response
object
13 properties 8 required
GET_Accessusers_GetAllAccessUsers_200_response
array
POST_Accessusers_CreateScans
array
GET_Accessusers_GetTicketsForAnEvent_200_response
object
2 properties
POST_Accessusers_CreateAnAccessUser
object
2 properties 1 required
AccessUserInfoResource
object
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vivenu-accessusers-api-openapi.yml Raw ↑

Other APIs vivenu publishes across the network.

vivenu access-lists 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
vivenu checkouts API
AE Profile APIs.io
#accessusers
← Back to V APIs
API Details
ID
vivenu:vivenu-accessusers-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-accessusers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/vivenu-accessusers-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 accessusers 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.