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

The supports API from vivenu — 14 operation(s) for supports.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 18 operations across 14 paths, and defines 11 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.

18 operations 14 paths 11 schemas 1 DELETE5 GET1 PATCH8 POST3 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 supports 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 18

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

supports 18
GET
/api/supports
Get all supports tickets
get_all_supports_tickets 9 params → 200400401
GET
/api/support/status
Count unfinished Support requests
count_unfinished_support_requests → 200401
GET
/api/support/{id}
Get a support ticket
get_a_support_ticket 2 params → 200400404
PUT
/api/support/{id}
Send a message
send_a_message 2 params body → 200400
GET
/api/supports/{id}
Get support ticket
get_support_ticket 1 param → 200400401404
PATCH
/api/supports/{id}
Patch a support ticket
patch_a_support_ticket 1 param body → 200400401
PUT
/api/supports/{id}
Update a support ticket
update_a_support_ticket 1 param body → 200400401
DELETE
/api/supports/{id}
Delete support ticket
delete_support_ticket 1 param → 200400401404
GET
/api/supports/{id}/context
Get support context
get_support_context 1 param → 200400401404
POST
/api/support
Create a support ticket
create_a_support_ticket body → 201400401
POST
/api/support/ticket-lookup
Look up the last transaction by email and resend the order confirmation
look_up_the_last_transaction_by_email_and_resend_the_order_confirmation body → 200400
POST
/api/supports/{id}/assign-seller
Update seller assignment
update_seller_assignment 1 param body → 200400401
POST
/api/supports/{id}/assignee
Change support ticket assignee
change_support_ticket_assignee 1 param body → 201400401
POST
/api/supports/{id}/message
Reply to support ticket
reply_to_support_ticket 1 param body → 201400401
POST
/api/supports/{id}/status
Change support ticket status
change_support_ticket_status 1 param body → 201400401
POST
/api/supports/{id}/seller
Change support ticket seller
change_support_ticket_seller 1 param body → 201400401
POST
/api/supports/{id}/prio
Change support ticket prio
change_support_ticket_prio 1 param body → 201400401
PUT
/api/supports/{id}/messages/{messageId}
Update a support message
update_a_support_message 2 params → 200400401

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are PublicSupportResource (18 properties), POST_Supports_CreateASupportTicket (7 properties), POST_Supports_ChangeSupportTicketPrio (1 property), PUT_Supports_UpdateASupportTicket (1 property). Each schema is shown below with its type and property counts.

POST_Supports_UpdateSellerAssignment
object
1 property 1 required
PATCH_Supports_PatchASupportTicket
object
1 property
POST_Supports_CreateASupportTicket
object
7 properties 3 required
POST_Supports_ChangeSupportTicketSeller
object
1 property 1 required
PublicSupportResource
object
18 properties 8 required
POST_Supports_ChangeSupportTicketAssignee
object
1 property 1 required
POST_Supports_ChangeSupportTicketStatus
object
1 property 1 required
PUT_Supports_UpdateASupportTicket
object
1 property
POST_Supports_ChangeSupportTicketPrio
object
1 property 1 required
PUT_Supports_SendAMessage
object
1 property 1 required
POST_Supports_ReplyToSupportTicket
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vivenu-supports-api-openapi.yml Raw ↑

Other APIs vivenu publishes across the network.

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