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

The customers API from vivenu — 23 operation(s) for customers.

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

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

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

27 operations 23 paths 25 schemas 2 DELETE14 GET9 POST2 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
Resource Areas
1

Authentication & Security 4

vivenu customers 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 27

Across 23 paths, the API surfaces 27 operations — 2 DELETE, 14 GET, 9 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

customers 27
GET
/api/customers/me
Get current customer
get_current_customer → 200401
POST
/api/customers/me
Update current customer
update_current_customer body → 200400401
GET
/api/customers/rich
Get all Customers
customers/list 7 params → 200400401
GET
/api/customers/tags
Get all Customer tags
get_all_customer_tags → 200401
GET
/api/customers/{id}
Get Customer
customers/get 1 param → 200400401404
PUT
/api/customers/{id}
Update Customer
customers/update 1 param body → 200400401404
DELETE
/api/customers/{id}
Delete Customer
customers/delete 1 param → 200400401
GET
/api/customers/me/payment-plans
Get payment plans of customer
get_payment_plans_of_customer 1 param → 200400401
GET
/api/customers/me/purchaseintents
Get PurchaseIntents of customer
get_purchase_intents_of_customer → 200401
GET
/api/customers/me/resell-offers
Get Resell Offers of Customer
customers/getCustomerResellOffers 3 params → 200400401
GET
/api/customers/me/shops
Get undershops of customer
get_undershops_of_customer 2 params → 200400401
GET
/api/customers/me/subscriptions
Get subscriptions of customer
get_subscriptions_of_customer 1 param → 200400401
GET
/api/customers/me/ticket-transfers
Get Ticket Transfers of Customer
customers/getCustomerTicketTransfers 5 params → 200400401
GET
/api/customers/me/tickets
Get tickets of customer
get_tickets_of_customer 3 params → 200400401
GET
/api/customers/me/transactions
Get transactions of customer
get_transactions_of_customer 3 params → 200400401
GET
/api/customers/password-reset/{token}
Reset password
reset_password 2 params → 200400
PUT
/api/customers/password-reset/{token}
Set a new password
set_a_new_password 1 param body → 200400
GET
/api/customers/{id}/balance
Get Customer Balance
customers/getCustomerBalance 1 param → 200400401404
POST
/api/customers
Create Customer
customers/create body → 200400401
POST
/api/customers/login
Login customer
login_customer body → 200400
POST
/api/customers/password-reset
Request a password reset mail
request_a_password_reset_mail body → 200400
POST
/api/customers/register
Register as a customer
register_as_a_customer body → 200400
POST
/api/customers/verify/resend
Resend verification mail
resend_verification_mail → 200401
POST
/api/customers/verify/{token}
Verify a Customer
verify_a_customer 2 params → 200400
POST
/api/customers/{id}/erase-data
Erase Customer data
erase_customer_data 1 param → 200401404
POST
/api/customers/{id}/account
Create account for Customer
create_account_for_customer 1 param body → 200400401404
DELETE
/api/customers/me/passkeys/{credentialId}
Delete customer passkey
delete_customer_passkey 1 param → 200400401

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are PublicEventResource (45 properties), PublicPurchaseIntentResource (43 properties), CustomerResource (23 properties), POST_Customers_CreateCustomer (18 properties). Each schema is shown below with its type and property counts.

POST_Customers_VerifyACustomer_200_response
object
1 property 1 required
GET_Customers_ResetPassword_200_response
object
1 property 1 required
GET_Customers_GetResellOffersOfCustomer_200_response
object
2 properties
POST_Customers_RequestAPasswordResetMail
object
2 properties 2 required
PublicPurchaseIntentResource
object
43 properties 14 required
PublicTicketTransferResource
object
10 properties 5 required
GET_Customers_GetAllCustomerTags_200_response
array
An array of tags
PUT_Customers_SetANewPassword_200_response
object
1 property 1 required
GET_Customers_GetTransactionsOfCustomer_200_response
object
2 properties
PUT_Customers_SetANewPassword
object
2 properties 2 required
GET_Customers_GetPurchaseIntentsOfCustomer_200_response
array
GET_Customers_GetAllCustomers_200_response
object
2 properties
CustomerResource
object
The associated customer which has been updated
23 properties 2 required
PublicResellOfferInfoResource
object
8 properties 7 required
POST_Customers_UpdateCurrentCustomer
object
4 properties
LegalIdentificationDocumentResource
POST_Customers_LoginCustomer
object
4 properties 3 required
POST_Customers_LoginCustomer_200_response
object
1 property 1 required
PUT_Customers_UpdateCustomer
object
17 properties
POST_Customers_CreateCustomer
object
18 properties 1 required
POST_Customers_CreateAccountForCustomer
object
1 property
GET_Customers_GetTicketsOfCustomer_200_response
object
2 properties
GET_Customers_GetTicketTransfersOfCustomer_200_response
object
2 properties
PublicEventResource
object
45 properties 4 required
GET_Customers_GetUndershopsOfCustomer_200_response
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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