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 payment-strategies API

The payment-strategies API from vivenu — 3 operation(s) for payment-strategies.

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

Tagged areas include payment-strategies. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 3 paths, and defines 7 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.

5 operations 3 paths 7 schemas 3 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 payment-strategies 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 5

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

payment-strategies 5
GET
/api/payments/strategies
Get Payment Strategies
get_payment_strategies 4 params → 200400401
POST
/api/payments/strategies
Create a Payment Strategy
create_a_payment_strategy body → 200400401
GET
/api/payments/strategies/{id}
Get a Payment Strategy
get_a_payment_strategy 1 param → 200400401404
PUT
/api/payments/strategies/{id}
Update a Payment Strategy
update_a_payment_strategy 1 param body → 200400401404
GET
/api/public/payments/strategies/{id}
Get Public Payment Strategy
get_public_payment_strategy 1 param → 200400404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are POST_Payment-strategies_CreateAPaymentStrategy_200_response (5 properties), GET_Payment-strategies_GetAPaymentStrategy_200_response (5 properties), PUT_Payment-strategies_UpdateAPaymentStrategy_200_response (5 properties), GET_Payment-strategies_GetPublicPaymentStrategy_200_response (5 properties). Each schema is shown below with its type and property counts.

GET_Payment-strategies_GetPublicPaymentStrategy_200_response
object
5 properties 5 required
PUT_Payment-strategies_UpdateAPaymentStrategy_200_response
object
5 properties 5 required
GET_Payment-strategies_GetAPaymentStrategy_200_response
object
5 properties 5 required
POST_Payment-strategies_CreateAPaymentStrategy
object
3 properties 3 required
GET_Payment-strategies_GetPaymentStrategies_200_response
object
2 properties
POST_Payment-strategies_CreateAPaymentStrategy_200_response
object
5 properties 5 required
PUT_Payment-strategies_UpdateAPaymentStrategy
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vivenu-payment-strategies-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 payment-strategies 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.