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

The Packages API from vivenu — 4 operation(s) for packages.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 6 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://vivenu.com, https://vivenu.dev.

6 operations 4 paths 6 schemas 4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
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 Packages 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 6

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

Packages 6
GET
/api/packages
Get api packages
getApiPackages 2 params → 200400401
GET
/api/packages/configs
Get api packages configs
getApiPackagesConfigs 3 params → 200400401
POST
/api/packages/configs
Create api packages configs
postApiPackagesConfigs body → 201400401
GET
/api/packages/{id}
Get api packages by id
getApiPackagesById 1 param → 200401
GET
/api/packages/configs/{id}
Get api packages configs by id
getApiPackagesConfigsById 1 param → 200401
PUT
/api/packages/configs/{id}
Replace api packages configs by id
putApiPackagesConfigsById 1 param body → 200400401

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PUT_Api_200_response (16 properties), GET_Api_200_response (16 properties), POST_Api_201_response (16 properties), PUT_Api (11 properties). Each schema is shown below with its type and property counts.

LanguageResource
stringnull
The preferred language of the package checkout
PUT_Api
object
11 properties
POST_Api_201_response
object
16 properties 10 required
POST_Api
object
5 properties 3 required
GET_Api_200_response
object
16 properties 9 required
PUT_Api_200_response
object
16 properties 10 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vivenu-packages-api-openapi.yml Raw ↑

Other APIs vivenu publishes across the network.

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