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

The users API from vivenu — 21 operation(s) for users.

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

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

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

25 operations 21 paths 9 schemas 4 DELETE7 GET10 POST4 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 users 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 25

Across 21 paths, the API surfaces 25 operations — 4 DELETE, 7 GET, 10 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

users 25
GET
/api/users
Get all Users
get_all_users → 200401
GET
/api/users/info
Get my User info
get_my_user_info → 200401
GET
/api/users/rich
Get Users rich
get_users_rich 7 params → 200400401
GET
/api/users/sellers
Get all Sellers of a User
get_all_sellers_of_a_user → 200401
GET
/api/users/info/{id}
Get User info
get_user_info 1 param → 200401
GET
/api/users/password-reset/{token}
Check if password reset exists
check_if_password_reset_exists 1 param → 200400
PUT
/api/users/password-reset/{token}
Set password after reset
set_password_after_reset 1 param body → 200400
GET
/api/users/{userId}/devices
Get user devices
get_user_devices 1 param → 200400401
POST
/api/users/access-seller
Change Seller on User
change_seller_on_user body → 200400401
POST
/api/users/invite
Invite a User
invite_a_user body → 201400401
POST
/api/users/login
Login a User
login_a_user body → 200400401
POST
/api/users/password-reset
Request a password reset mail
request_a_password_reset_mail body → 200400
POST
/api/users/refresh
Refresh authentication token
refresh_authentication_token body → 200400401
POST
/api/users/notifications/deviceinfo
Get notification device info
get_notification_device_info body → 200400401
POST
/api/users/notifications/subscribe
Subscribe notification type
subscribe_notification_type body → 200400401
POST
/api/users/notifications/unsubscribe
Unsubscribe notification type
unsubscribe_notification_type body → 200400401
POST
/api/users/{id}/roles
Add User roles
add_user_roles 1 param body → 200400401
DELETE
/api/users/{id}/roles
Remove User roles
remove_user_roles 1 param body → 200400401
POST
/api/users/{id}/permissions
Add User permissions
add_user_permissions 1 param body → 200400401
DELETE
/api/users/{id}/permissions
Remove User permissions
remove_user_permissions 1 param body → 200400401
PUT
/api/users/{id}
Update User info
update_user_info 1 param body → 200400401
DELETE
/api/users/{id}
Delete a User
delete_a_user 1 param → 200401
PUT
/api/users/{id}/logintype
Update User Login Type
update_user_login_type 1 param body → 200400401
PUT
/api/users/{userId}/sellers/add
Add Seller to a User
add_seller_to_a_user 1 param body → 200400401
DELETE
/api/users/{userId}/sellers/remove
Remove a Seller of a User
remove_a_seller_of_a_user 1 param body → 200400401

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are POST_Users_SubscribeNotificationType (4 properties), PUT_Users_AddSellerToAUser (2 properties), POST_Users_UnsubscribeNotificationType (2 properties), DELETE_Users_RemoveASellerOfAUser (1 property). Each schema is shown below with its type and property counts.

PUT_Users_AddSellerToAUser
object
2 properties 1 required
POST_Users_ChangeSellerOnUser
object
1 property 1 required
POST_Users_UnsubscribeNotificationType
object
2 properties 2 required
DELETE_Users_RemoveASellerOfAUser
object
1 property 1 required
POST_Users_RefreshAuthenticationToken
object
1 property
POST_Users_GetNotificationDeviceInfo
object
1 property 1 required
PUT_Users_UpdateUserInfo
object
1 property 1 required
POST_Users_SubscribeNotificationType
object
4 properties 4 required
POST_Users_RequestAPasswordResetMail
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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