USDA Hardiness Zone API
Overview
To use USDA Hardiness Zone, 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/hardinesszoneExample
How to call the USDA Hardiness Zone API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/hardinesszone?zip=97201" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/hardinesszone?zip=97201', {
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/hardinesszone?zip=97201', 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/hardinesszone?zip=97201", 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": {
"zipCode": "97201",
"zone": "8b",
"tempRange": "15 to 20",
"zoneTitle": "8b: 15 to 20",
"details": {
"tempRange": "15°F to 20°F (-9°C to -7°C)",
"description": "Mild and relatively warm, found in parts of southern U.S. like the Gulf Coast and parts of Texas.",
"plantSurvival": "A wide range of plants, including many Mediterranean and subtropical varieties."
}
}
}Authentication
The USDA Hardiness Zone 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 USDA Hardiness Zone API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the USDA Hardiness Zone API:
Get Hardiness Zone Data
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
zip | string | required | The zip code to get the USDA Plant Hardiness Zone for Length: 5 - 5 chars | - |
Response
The USDA Hardiness Zone 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>
<zipCode>97201</zipCode>
<zone>8b</zone>
<tempRange>15 to 20</tempRange>
<zoneTitle>8b: 15 to 20</zoneTitle>
<details>
<tempRange>15°F to 20°F (-9°C to -7°C)</tempRange>
<description>Mild and relatively warm, found in parts of southern U.S. like the Gulf Coast and parts of Texas.</description>
<plantSurvival>A wide range of plants, including many Mediterranean and subtropical varieties.</plantSurvival>
</details>
</data>
</response>
status: ok
error: null
data:
zipCode: '97201'
zone: 8b
tempRange: 15 to 20
zoneTitle: '8b: 15 to 20'
details:
tempRange: 15°F to 20°F (-9°C to -7°C)
description: >-
Mild and relatively warm, found in parts of southern U.S. like the Gulf
Coast and parts of Texas.
plantSurvival: >-
A wide range of plants, including many Mediterranean and subtropical
varieties.
| key | value |
|---|---|
| zipCode | 97201 |
| zone | 8b |
| tempRange | 15 to 20 |
| zoneTitle | 8b: 15 to 20 |
| details | {tempRange:15°F to 20°F (-9°C to -7°C),description:Mild and relatively warm, found in parts of southern U.S. like the Gulf Coast and parts of Texas.,plantSurvival:A wide range of plants, including many Mediterranean and subtropical varieties.} |
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 |
|---|---|---|---|
zipCode | string | The input ZIP code provided in the request | |
zonePremium | string | USDA hardiness zone classification code | |
tempRange | string | Temperature range for the zone in Fahrenheit | |
zoneTitle | string | Formatted title with zone and temperature range | |
details | object | - | |
â”” tempRangePremium | string | Detailed temperature range in Fahrenheit and Celsius | |
â”” descriptionPremium | string | Description of climate conditions for the zone | |
â”” plantSurvivalPremium | string | Types of plants suitable for the hardiness zone |
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 USDA Hardiness Zone through GraphQL to combine it with other API calls in a single request. Query only the usda hardiness zone 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 {
hardinesszone(
input: {
zip: "97201"
}
) {
zipCode
zone
tempRange
zoneTitle
details {
tempRange
description
plantSurvival
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The USDA Hardiness Zone 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
USDA Hardiness Zone 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 USDA Hardiness Zone 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 USDA Hardiness Zone
Official USDA Hardiness Zone packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
USDA Hardiness Zone 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 USDA Hardiness Zone?
How many credits does USDA Hardiness Zone cost?
Each successful USDA Hardiness Zone 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 usda hardiness zone lookups.
Can I use USDA Hardiness Zone in production?
The free plan is for testing and development only. For production use of USDA Hardiness Zone, 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 USDA Hardiness Zone from a browser?
What happens if I exceed my USDA Hardiness Zone credit limit?
When you reach your monthly credit limit, USDA Hardiness Zone 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.








