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

Workflow execution history and status

Ava Protocol Executions 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 Execution. The published artifact set on APIs.io includes an OpenAPI specification.

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

8 operations 8 paths 16 schemas 7 GET1 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 Executions 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 8

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

Executions 8

Workflow execution history and status

GET
/executions
List executions
listExecutions 4 params → 200401
GET
/workflows/{id}/executions
List executions for a workflow (convenience nested route)
listExecutionsForWorkflow 4 params → 200401404
GET
/executions/{id}
Retrieve an execution (full payload with steps)
getExecution 2 params → 200401404
GET
/executions/{id}:getStatus
Get execution status (lightweight, no steps)
getExecutionStatus 2 params → 200401404
POST
/executions/{id}:signal
Deliver an approval/external signal to a waiting execution
signalExecution 2 params body → 200400401404
GET
/executions/{id}:stream
Stream execution status changes (Server-Sent Events)
streamExecution 3 params → 200401404
GET
/executions:count
Count executions
countExecutions 1 param → 200401
GET
/executions:stats
Execution statistics (totals + averages)
executionStats 1 param → 200401

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are ExecutionStep (17 properties), Execution (12 properties), ExecutionStatusSummary (6 properties), Problem (6 properties). Each schema is shown below with its type and property counts.

ExecutionTier
string
Pricing group for value-capture fees.
Fee
object
2 properties 2 required
ExecutionList
object
2 properties 2 required
Execution
object
12 properties 4 required
PageInfo
object
4 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…
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
Ulid
string
ULID identifier (26-char Crockford base32).
ExecutionStats
object
5 properties 3 required
ExecutionCount
object
1 property 1 required
NodeCOGS
object
4 properties 3 required
ValueFee
object
6 properties 2 required
ExecutionStatus
string
Outcome of an execution. pending is in-flight; waiting is suspended mid-workflow at an await node, durably parked until a signal arrives (a human approve/rejec…
SignalExecutionRequest
object
2 properties 1 required
ExecutionStatusSummary
object
Lightweight execution status (no steps payload).
6 properties 2 required
ExecutionStep
object
One node (or trigger) invocation within an Execution. The type field is the trigger or node type name (e.g., cron, contractWrite); the corresponding output is…
17 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Ava Protocol publishes across the network.

Ava Protocol Auth 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 Wallets API
Ava Protocol Workflows API
Where this information came from

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