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

Zavu Sub-Accounts API

The Sub-Accounts API from Zavu — 5 operation(s) for sub-accounts.

Zavu Sub-Accounts API is one of 21 APIs that Zavu publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Subaccounts. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

This API exposes 9 operations across 5 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 0.2.0.

Requests are made against a single base URL, https://api.zavu.dev.

9 operations 5 paths 9 schemas 2 DELETE4 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.2.0
Base URL
https://api.zavu.dev/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Zavu Sub-Accounts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 9

Across 5 paths, the API surfaces 9 operations — 2 DELETE, 4 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Sub-Accounts 9
POST
/v1/sub-accounts
Create sub-account
createSubAccount body → 201400401403
GET
/v1/sub-accounts
List sub-accounts
listSubAccounts 2 params → 200401403
GET
/v1/sub-accounts/{id}
Get sub-account
getSubAccount 1 param → 200401403404
PATCH
/v1/sub-accounts/{id}
Update sub-account
updateSubAccount 1 param body → 200400401403404
DELETE
/v1/sub-accounts/{id}
Deactivate sub-account
deactivateSubAccount 1 param → 200401403404
GET
/v1/sub-accounts/{id}/balance
Get sub-account spending
getSubAccountBalance 1 param → 200401403404
GET
/v1/sub-accounts/{id}/api-keys
List sub-account API keys
listSubAccountApiKeys 1 param → 200401403404
POST
/v1/sub-accounts/{id}/api-keys
Create sub-account API key
createSubAccountApiKey 1 param body → 201400401403404
DELETE
/v1/sub-accounts/{id}/api-keys/{keyId}
Revoke sub-account API key
revokeSubAccountApiKey 2 params → 204401403404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are SubAccount (9 properties), SubAccountApiKey (9 properties), BalanceResponse (5 properties), SubAccountUpdateRequest (5 properties). Each schema is shown below with its type and property counts.

SubAccountStatus
string
SubAccount
object
9 properties 5 required
SubAccountApiKey
object
9 properties 5 required
SubAccountUpdateRequest
object
5 properties
SubAccountResponse
object
1 property 1 required
SubAccountCreateRequest
object
4 properties 1 required
SubAccountApiKeyCreateRequest
object
3 properties 1 required
BalanceResponse
object
5 properties 2 required
Error
object
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zavu-sub-accounts-api-openapi.yml Raw ↑

Other APIs Zavu publishes across the network.

Zavu 10DLC API
Zavu Account API
Zavu Agent Flows API
Zavu Agent Knowledge Bases API
Zavu Agent Tools API
Zavu Agents API
Zavu Balance API
Zavu Broadcasts API
Zavu Contacts API
Zavu Functions API
Zavu Introspect API
Zavu Invitations API
Where this information came from

This is an independent, third-party profile of Zavu Sub-Accounts 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.