USDA Hardiness Zone API GET

Documentation Start for free →

Hardiness Zone is a simple tool for getting the USDA Plant Hardiness Zone for a given zip code

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/hardinesszone

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // USDA Hardiness Zone response payload
  }
}

About the USDA Hardiness Zone API

Hardiness Zone works by analyzing the data provided and returning the USDA Plant Hardiness Zone for the given location. It uses various sources to determine the USDA Plant Hardiness Zone for the given location and returns the data.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use USDA Hardiness Zone

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the USDA Hardiness Zone API.

Read the docs →

What does the USDA Hardiness Zone API do?

Hardiness Zone is a simple tool for getting the USDA Plant Hardiness Zone for a given zip code

How do I authenticate USDA Hardiness Zone API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the USDA Hardiness Zone API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the USDA Hardiness Zone API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the USDA Hardiness Zone API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the USDA Hardiness Zone API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/hardinesszone

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`zip`Required	string	`97201`	The zip code to get the USDA Plant Hardiness Zone for length 5-5

Example request

1
2

curl "https://api.apiverve.com/v1/hardinesszone?zip=97201" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/hardinesszone

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample 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."
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`zipCode`	string	`"97201"`	The input ZIP code provided in the request
`zone`Premium	string	`"8b"`	USDA hardiness zone classification code
`tempRange`	string	`"15 to 20"`	Temperature range for the zone in Fahrenheit
`zoneTitle`	string	`"8b: 15 to 20"`	Formatted title with zone and temperature range
`details`	object	`{...}`
`tempRange`Premium	string	`"15°F to 20°F (-9°C to -7°C)"`	Detailed temperature range in Fahrenheit and Celsius
`description`Premium	string	`"Mild and relatively warm, found in parts of southern U.S. like the Gulf Coast and parts of Texas."`	Description of climate conditions for the zone
`plantSurvival`Premium	string	`"A wide range of plants, including many Mediterranean and subtropical varieties."`	Types of plants suitable for the hardiness zone

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	USDA Hardiness Zone calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/hardinesszone

No SDK to install — this is a plain HTTPS call to /v1/hardinesszone with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/hardinesszone" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/hardinesszone-apiSource, issues and the examples this page is built from.ReferenceUSDA Hardiness Zone API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/hardinesszonenpm APIVerve.API.USDAHardinessZoneNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/hardinesszone

Install the Node.js SDK, then call the USDA Hardiness Zone API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/hardinesszone

Node.js

const res = await fetch("https://api.apiverve.com/v1/hardinesszone", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/hardinesszoneThe published Node.js client, versioned and signed.GitHubapiverve/hardinesszone-apiSource, issues and the examples this page is built from.ReferenceUSDA Hardiness Zone API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.USDAHardinessZoneNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/hardinesszone

No SDK to install — this is a plain HTTPS call to /v1/hardinesszone with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/hardinesszone",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/hardinesszonenpm APIVerve.API.USDAHardinessZoneNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/hardinesszone

Install the C# / .NET SDK, then call the USDA Hardiness Zone API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.USDAHardinessZone

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/hardinesszone");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.USDAHardinessZoneThe published C# / .NET client, versioned and signed.GitHubapiverve/hardinesszone-apiSource, issues and the examples this page is built from.ReferenceUSDA Hardiness Zone API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/hardinesszonenpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/hardinesszone

No SDK to install — this is a plain HTTPS call to /v1/hardinesszone with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/hardinesszone", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/hardinesszonenpm APIVerve.API.USDAHardinessZoneNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/hardinesszone

No SDK to install — this is a plain HTTPS call to /v1/hardinesszone with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/hardinesszone");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/hardinesszonenpm APIVerve.API.USDAHardinessZoneNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/hardinesszone

No SDK to install — this is a plain HTTPS call to /v1/hardinesszone with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/hardinesszone")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/hardinesszonenpm APIVerve.API.USDAHardinessZoneNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

Multi-Currency E-commerce: Stop Losing SalesShowing prices in local currency increases conversions 20-40%. Here's how to implement multi-currency pricing that actually works.Read

Location APIs: Distance, Geocoding, and TimezonesBuild location-aware features without Google Maps pricing. Distance calculations, address lookup, timezone handling—all from one API.Read

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

USDA Hardiness Zone API GET

Try it — live request, no key required

About the USDA Hardiness Zone API

Ways to call it

Other ways to use USDA Hardiness Zone

Questions.

Request parameters — GET /v1/hardinesszone

Required

Authentication

Response — GET /v1/hardinesszone

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/hardinesszone

Resources

Also published for

Call it from Node.js — GET /v1/hardinesszone

Resources

Also published for

Call it from Python — GET /v1/hardinesszone

Resources

Also published for

Call it from C# / .NET — GET /v1/hardinesszone

Resources

Also published for

Call it from Go — GET /v1/hardinesszone

Resources

Also published for

Call it from PHP — GET /v1/hardinesszone

Resources

Also published for

Call it from Ruby — GET /v1/hardinesszone

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — USDA Hardiness Zone API

Geography

Related articles

Ready to build with USDA Hardiness Zone? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog