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

Ava Protocol Wallets API

Smart-wallet derivation and operations

Ava Protocol Wallets API is one of 10 APIs that Ava Protocol publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 3 base URLs: https://gateway.avaprotocol.org/api/v1, https://gateway-staging.avaprotocol.org/api/v1, http://localhost:8080/api/v1.

5 operations 4 paths 11 schemas 2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://gateway.avaprotocol.org/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Ava Protocol Wallets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — JWT bearer token. Obtained via POST /auth:exchange (wallet signature flow) or via the operator-run create-api-key CLI (long-lived, server-to-server). Send on e…

Paths & Operations 5

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

Wallets 5

Smart-wallet derivation and operations

GET
/wallets
List the authenticated user's smart wallets
listWallets → 200401
POST
/wallets
Derive (and persist) a smart wallet address from (owner, salt, factory)
createWallet body → 200201400401
PATCH
/wallets/{address}
Update wallet properties
updateWallet 1 param body → 200401404
POST
/wallets/{address}:withdraw
Withdraw funds from a smart wallet
withdrawWallet 1 param body → 200400401404412
GET
/wallets/{address}:getNonce
Get the smart wallet's current nonce
getWalletNonce 2 params → 200401404

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are WithdrawResponse (9 properties), Wallet (9 properties), Problem (6 properties), WithdrawRequest (4 properties). Each schema is shown below with its type and property counts.

EthereumAddress
string
Lowercase or checksummed hex EOA / contract address.
NonceResponse
object
1 property 1 required
Hex
string
Arbitrary-length hex-encoded byte string.
WalletList
object
1 property 1 required
CreateWalletRequest
object
3 properties 1 required
WithdrawResponse
object
9 properties 1 required
Wallet
object
9 properties 2 required
ChainId
integer
Numeric chain ID (e.g. 11155111 for Sepolia, 8453 for Base). On chain-aware trigger/node configs this is required and must be a configured chain; on query/filt…
UpdateWalletRequest
object
1 property
WithdrawRequest
object
4 properties 3 required
Problem
object
RFC 7807 problem+json. Returned as application/problem+json on any 4xx/5xx response. type and title describe the error class; detail is human-readable; instanc…
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ava-protocol-wallets-api-openapi.yml Raw ↑

Other APIs Ava Protocol publishes across the network.

Ava Protocol Auth API
Ava Protocol Executions API
Ava Protocol Health API
Ava Protocol Nodes API
Ava Protocol Operators API
Ava Protocol Secrets API
Ava Protocol Tokens API
Ava Protocol Triggers API
Ava Protocol Workflows API
Where this information came from

This is an independent, third-party profile of Ava Protocol Wallets 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.