Treasury Yields API
Overview
To use Treasury Yields, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/treasuryyieldsExample
How to call the Treasury Yields API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/treasuryyields?date=2025-06&type=10yr" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/treasuryyields?date=2025-06&type=10yr', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/treasuryyields?date=2025-06&type=10yr', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/treasuryyields?date=2025-06&type=10yr", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"date": "2024-02-01",
"bills": 5.24,
"notes": 4.35,
"bonds": 4.67,
"tips": 2.15,
"frn": 5.31,
"changes": {
"bills": {
"change1d": 0.02,
"direction": "up"
},
"notes": {
"change1d": -0.03,
"direction": "down"
},
"bonds": {
"change1d": 0.01,
"direction": "up"
},
"tips": {
"change1d": 0,
"direction": "unchanged"
},
"frn": {
"change1d": 0.02,
"direction": "up"
}
},
"previousDate": "2024-01-31"
}
}Authentication
The Treasury Yields API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Treasury Yields API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Treasury Yields API:
Get Treasury Yields
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
datePremium | string | optional | Optional month in YYYY-MM format for a recent-month lookup (recent months only). Omit for current data. | - | |
typePremium | string | optional | Optional filter for a single point. Legacy security types: bills, notes, bonds, tips, frn. Or a maturity: 1mo, 3mo, 6mo, 1yr, 2yr, 3yr, 5yr, 7yr, 10yr, 20yr, 30yr | - |
Response
The Treasury Yields API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<date>2024-02-01</date>
<bills>5.24</bills>
<notes>4.35</notes>
<bonds>4.67</bonds>
<tips>2.15</tips>
<frn>5.31</frn>
<changes>
<bills>
<change1d>0.02</change1d>
<direction>up</direction>
</bills>
<notes>
<change1d>-0.03</change1d>
<direction>down</direction>
</notes>
<bonds>
<change1d>0.01</change1d>
<direction>up</direction>
</bonds>
<tips>
<change1d>0</change1d>
<direction>unchanged</direction>
</tips>
<frn>
<change1d>0.02</change1d>
<direction>up</direction>
</frn>
</changes>
<previousDate>2024-01-31</previousDate>
</data>
</response>
status: ok
error: null
data:
date: '2024-02-01'
bills: 5.24
notes: 4.35
bonds: 4.67
tips: 2.15
frn: 5.31
changes:
bills:
change1d: 0.02
direction: up
notes:
change1d: -0.03
direction: down
bonds:
change1d: 0.01
direction: up
tips:
change1d: 0
direction: unchanged
frn:
change1d: 0.02
direction: up
previousDate: '2024-01-31'
| key | value |
|---|---|
| date | 2024-02-01 |
| bills | 5.24 |
| notes | 4.35 |
| bonds | 4.67 |
| tips | 2.15 |
| frn | 5.31 |
| changes | {bills:{change1d:0.02,direction:up},notes:{change1d:-0.03,direction:down},bonds:{change1d:0.01,direction:up},tips:{change1d:0,direction:unchanged},frn:{change1d:0.02,direction:up}} |
| previousDate | 2024-01-31 |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
date | string | The date of the treasury yields data in YYYY-MM-DD format | |
billsPremium | number | Benchmark short-term yield (3-month) as percentage | |
notesPremium | number | Benchmark note yield (10-year) as percentage | |
bonds | number | Benchmark long bond yield (30-year) as percentage | |
tipsPremium | number | Benchmark TIPS real yield (10-year) as percentage | |
frnPremium | number | Floating Rate Note reference yield (3-month bill) as percentage | |
changesPremium | object | Day-over-day change statistics, keyed by legacy type and by maturity | |
â”” billsPremium | object | Change data for the 3-month benchmark including change1d and direction | |
â”” change1dPremium | number | One-day percentage point change for the 3-month benchmark | |
â”” direction | string | Direction of change: up, down, or unchanged | |
â”” notesPremium | object | Change data for the 10-year benchmark including change1d and direction | |
â”” change1dPremium | number | One-day percentage point change for the 10-year benchmark | |
â”” direction | string | Direction of change: up, down, or unchanged | |
â”” bondsPremium | object | Change data for the 30-year benchmark including change1d and direction | |
â”” change1dPremium | number | One-day percentage point change for the 30-year benchmark | |
â”” direction | string | Direction of change: up, down, or unchanged | |
â”” tipsPremium | object | Change data for the 10-year TIPS benchmark including change1d and direction | |
â”” change1dPremium | number | One-day percentage point change for the 10-year TIPS benchmark | |
â”” direction | string | Direction of change: up, down, or unchanged | |
â”” frnPremium | object | Change data for the FRN reference (3-month) including change1d and direction |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Treasury Yields through GraphQL to combine it with other API calls in a single request. Query only the treasury yields data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
treasuryyields(
input: {
date: "2025-06"
type: "10yr"
}
) {
date
bills
notes
bonds
tips
frn
changes {
bills {
change1d
direction
}
notes {
change1d
direction
}
bonds {
change1d
direction
}
tips {
change1d
direction
}
frn {
change1d
direction
}
}
previousDate
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Treasury Yields API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Treasury Yields requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Treasury Yields API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Treasury Yields
Official Treasury Yields packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Treasury Yields works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Treasury Yields?
How many credits does Treasury Yields cost?
Each successful Treasury Yields API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful treasury yields lookups.
Can I use Treasury Yields in production?
The free plan is for testing and development only. For production use of Treasury Yields, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Treasury Yields from a browser?
What happens if I exceed my Treasury Yields credit limit?
When you reach your monthly credit limit, Treasury Yields API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








