What the response contains
Try hound, retriever, and beagle and use the returned fields to identify the right record.
Fields worth checking
- Breed photo
- Breed name
- Image link
Dog CEO
Breed photo · Breed name · Image link
Live lookup
Type a real query, scan the cards and confirm the key details before opening the full source.
Quick examples
The breed list and an image use different responses
/breeds/list/all returns an object of breeds and sub-breeds in message. /breed/{breed}/images/random instead returns an image URL in message and the response status. Confirm a breed identifier in the list first, then use it in the image path. This keeps an interface from searching for spelling the source does not recognise.
- Read status before using message as a result.
- Use the breed list for options and validation.
- A breed with sub-breeds appears as a key with a related list.
A photo is visual reference, not confirmation
The random route returns an image associated with the requested path. It can support a gallery or exploration experience, but it does not confirm lineage, health, temperament, age, or the identity of an animal. Do not use one image to diagnose or identify a real dog.
- Attribute the image to the source and retain its returned URL.
- Do not promise that a photo represents every dog of a breed.
- Seek appropriate professional guidance for identification or care.
Query again when another image is needed
The random response intentionally varies: a new request can return another URL. Retain a chosen image when it is part of a publication or reviewable selection; request again when a gallery should vary. Treat the response as visual reference material, not a stable catalogue of animals.
- Save the displayed URL when a page must be reproducible.
- Show an error state when status does not indicate success.
- Keep breed lookup separate from choosing a random image.
