Overview
This guide walks through every capability of the Yield.xyz Programmatic API. Use it to automate project provisioning, API key lifecycle, yield enablement, fee configuration, and reporting — all without touching the dashboard.For background on what Programmatic Access is and when to use it, see the Programmatic Access documentation.
Prerequisites
Before you begin, you need a Programmatic Access API Key:1
Log in to the dashboard
Go to dashboard.yield.xyz
2
Open the Developers section
Click your avatar (top-right) → </> Developers
3
Create an Admin API Key
Click Create API Key and store the key securely — it is only displayed once

Projects
A project maps to a logical grouping — typically one per client, workspace, or environment. Each project has its own API keys, enabled yields, and fee configurations.Create a Project
List Projects
Update a Project
Delete a Project
API Keys
API keys are scoped to a project. These are the keys your application passes to the Yield API (X-API-KEY header) for staking, balance, and action requests.
Create a Key
List Keys
Update a Key
Delete a Key
Enabled Yields
Control which yield integrations are available for a project. An integration is a specific yield opportunity identified by anintegrationId (e.g., ethereum-eth-lido-staking, optimism-usdt-aave-v3-lending).
List Enabled Yields
Enable Yields (Bulk)
Disable a Single Yield
Disable Yields (Bulk)
Fee Configuration
Configure fees on a per-integration basis within a project. Fees are expressed in basis points (bps), where 100 bps = 1%.Applying fees may require Yield.xyz to deploy onchain infrastructure (e.g., an OAV or fee wrapper). The fee configuration status reflects this lifecycle:
REQUESTED → PROCESSING → LIVE.Create a Fee Configuration
List Fee Configurations
Update a Fee Configuration
null for a fee field to remove it.
Delete a Fee Configuration
Reports
Pull transaction and staking activity across all projects belonging to your team. Use query parameters to filter and sort results.List Report Entries
Response:
Recommended Provisioning Flow
A typical integration follows this sequence when onboarding a new client or workspace:1
Create a project
POST /v1/programmatic/projects — one project per client or workspace2
Mint an API key
POST /v1/programmatic/projects/{projectId}/keys — the key is used by the client or your backend to call the Yield API3
Enable yields
POST /v1/programmatic/projects/{projectId}/yields/enabled — enable a curated set of yield integrations4
Configure fees (optional)
POST /v1/programmatic/projects/{projectId}/fee-configuration — apply deposit, management, or performance fees5
Monitor with reports
GET /v1/programmatic/report-entries — pull activity data for reconciliation and analyticsFee Configuration Lifecycle
When a fee configuration is created, it may go through several statuses before becoming active:Some fee configurations require Yield.xyz to deploy a dedicated Optimized Allocator Vault (OAV) or fee wrapper contract onchain. This is handled automatically — the
status field reflects the deployment progress.OpenAPI Specification
The full OpenAPI specification for the Programmatic API is available directly in the Yield.xyz dashboard:- Log in to dashboard.yield.xyz
- Click your avatar → </> Developers
- The OpenAPI spec is displayed in the developer section

Next Steps
Programmatic Access Docs
Overview of capabilities and authentication
Fee Configuration
Learn more about how fees work in Yield.xyz
Projects & API Keys
Understand project and key concepts
OAVs
Learn about Optimized Allocator Vaults

