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

The vouchers API from vivenu — 5 operation(s) for vouchers.

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

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

This API exposes 7 operations across 5 paths, and defines 6 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 5 paths 6 schemas 5 GET1 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
Resource Areas
1

Authentication & Security 4

vivenu vouchers 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 5 paths, the API surfaces 7 operations — 5 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

vouchers 7
GET
/api/vouchers
Get all Vouchers
vouchers/list 4 params → 200400401
POST
/api/vouchers
Create a Voucher
vouchers/create body → 201400401
GET
/api/vouchers/richdeprecated
Get all Vouchers
get_all_vouchers 4 params → 200400401
GET
/api/vouchers/{id}
Get Voucher by id
get_voucher_by_id 1 param → 200400401404
PUT
/api/vouchers/{id}
Update a Voucher
vouchers/update 1 param body → 200400401404
GET
/api/vouchers/{id}/transactions
Get Voucher Transactions by id
vouchers/getTransactions 1 param → 200400401404
GET
/api/vouchers/{id}/{code}/info
Get Voucher by id and code
get_voucher_by_id_and_code 2 params → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are VoucherWithBalanceResource (12 properties), VoucherResource (11 properties), GET_Vouchers_GetVoucherByIdAndCode_200_response (5 properties), POST_Vouchers_CreateAVoucher (3 properties). Each schema is shown below with its type and property counts.

PUT_Vouchers_UpdateAVoucher
object
2 properties 1 required
POST_Vouchers_CreateAVoucher
object
3 properties 1 required
GET_Vouchers_GetAllVouchers_200_response
object
2 properties
VoucherWithBalanceResource
object
12 properties 5 required
GET_Vouchers_GetVoucherByIdAndCode_200_response
object
5 properties
VoucherResource
object
11 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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