Dog Breeds is a simple tool for getting information about dog breeds. It returns information such as breed name, temperament, lifespan, and more.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Dog Breeds response payload
}
}
About the Dog Breeds API
Dog Breeds works by providing information about various dog breeds. It returns information such as breed name, temperament, lifespan, and more. The information is sourced from reputable sources to ensure accuracy.
What people use it for
- Pet Care
- Use the Dog Breeds API to get information about dog breeds for pet care. Use the data to learn about different breeds, understand their characteristics, and provide better care
- Breed Selection
- Get information about dog breeds by using the Dog Breeds API for breed selection. Use the data to compare breeds, choose the right breed, and make informed decisions
- Training Assistance
- Use the Dog Breeds API to get information about dog breeds for training assistance. Use the data to understand breed behavior, tailor training methods, and improve results
- Breed Identification
- Get information about dog breeds by using the Dog Breeds API for breed identification. Use the data to identify breeds, learn about their traits, and enhance knowledge
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
Other ways to use Dog Breeds
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Dog Breeds API do?
How do I authenticate Dog Breeds API requests?
How much does the Dog Breeds API cost?
How fast is the Dog Breeds API?
What response formats does the Dog Breeds API support?
What HTTP method does the Dog Breeds API use?
Request parameters — GET /v1/dogbreeds
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 |
|---|---|---|---|
breedRequired | string | beagle | The name of the dog breed to get information about |
curl "https://api.apiverve.com/v1/dogbreeds?breed=beagle" \
-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-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
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/dogbreeds
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.
{
"status": "ok",
"error": null,
"data": {
"breed": "beagle",
"foundCount": 1,
"foundBreeds": [
{
"name": "Beagle",
"weight": {
"lowerLbs": 20,
"upperLbs": 35
},
"height": {
"lowerInches": 13,
"upperInches": 15
},
"bredFor": "rabbit, hare hunting",
"group": "hound",
"life_span": {
"lowerYears": 13,
"upperYears": 16
},
"traits": [
"amiable",
"even tempered",
"excitable",
"determined",
"gentle",
"intelligent"
]
}
]
}
}
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 |
|---|---|---|---|
breed | string | "beagle" | The requested dog breed name in lowercase |
foundCount | number | 1 | Number of breed matches found in database |
foundBreeds | array[1] | Array of dog breed objects matching search criteria | |
name | string | "Beagle" | Official breed name with proper capitalization |
weight | object | {...} | |
lowerLbsPremium | number | 20 | Minimum weight range for breed in pounds |
upperLbsPremium | number | 35 | Maximum weight range for breed in pounds |
height | object | {...} | |
lowerInchesPremium | number | 13 | Minimum height range for breed in inches |
upperInchesPremium | number | 15 | Maximum height range for breed in inches |
bredForPremium | string | "rabbit, hare hunting" | Historical purpose or original breeding purpose |
group | string | "hound" | Official breed group classification by kennel clubs |
life_span | object | {...} | |
lowerYearsPremium | number | 13 | Minimum life expectancy of breed in years |
upperYearsPremium | number | 16 | Maximum life expectancy of breed in years |
traitsPremium | array | [amiable, ...] | Array of distinctive personality and behavioral characteristics |
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 | Dog Breeds 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.
Call it from cURL — GET /v1/dogbreeds
No SDK to install — this is a plain HTTPS call to /v1/dogbreeds with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/dogbreeds" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
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/dogbreeds
Install the Node.js SDK, then call the Dog Breeds API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/dogbreedsconst res = await fetch("https://api.apiverve.com/v1/dogbreeds", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/dogbreeds
Install the Python SDK, then call the Dog Breeds API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-dogbreedsimport requests
res = requests.get(
"https://api.apiverve.com/v1/dogbreeds",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
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/dogbreeds
Install the C# / .NET SDK, then call the Dog Breeds API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.DogBreedsusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/dogbreeds");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/dogbreeds
No SDK to install — this is a plain HTTPS call to /v1/dogbreeds 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/dogbreeds", 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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/dogbreeds
No SDK to install — this is a plain HTTPS call to /v1/dogbreeds with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/dogbreeds");
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
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/dogbreeds
No SDK to install — this is a plain HTTPS call to /v1/dogbreeds with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/dogbreeds")
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.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Dog Breeds form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Dog Breeds API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Dog Breeds API.
Data Lookup
- ASN Lookup
- Bible
- Country Calling Code
- Dictionary
- Dog Breeds
- Emoji Lookup
- Gender Detector
- Gravatar Lookup
- IP Demographics
- Lottery Numbers
- Nobel Prizes
- Open Source Licenses
- Thesaurus
- Timezone Lookup
- Unicode Character Lookup
- World Time
- ZIP Demographics
Related articles
All articles →
The Timezone Bug That Cost Us a ClientA scheduled email went out at 3 AM instead of 9 AM. The client wasn't happy. Here's what went wrong.Read
Build a Lead Enrichment Pipeline That Actually WorksTurn email addresses into full customer profiles. Location, company, social links—automatically. Here's how to build it.Read
Weather APIs: Build a Dashboard That's Actually UsefulCurrent conditions, forecasts, air quality, sunrise times—here's how to build a weather dashboard users will love.Read