Swagger Petstore - OpenAPI 3.0
PUT/pet

Replace a pet in the store

Replaces an existing pet's details in the store. Supply name and photoUrls, and include the pet's id to identify it; status can be available, pending, or sold. You can send the pet data as JSON, XML, or URL-encoded form data.

6 body fields

Pet details to replace the existing store record. Supply name and photoUrls; the body can use JSON, XML, or URL-encoded form data.

idintegeroptional
The pet's identifier.
namestringrequired
The pet's name.
categoryobjectoptional
The pet's category, with an identifier and name.
photoUrlsarray<string>required
URLs for photos of the pet.
tagsarray<object>optional
Tags associated with the pet, each with an identifier and name.
statusstringoptional
pet status in the store
Allowed:availablependingsold

5 status codes
200Returns the updated pet object, including its current pet details.
idintegeroptional
namestringrequired
categoryobjectoptional
photoUrlsarray<string>required
tagsarray<object>optional
statusstringoptional
pet status in the store
Allowed:availablependingsold
400Returned when the supplied pet ID is invalid.
404Returned when the pet does not exist.
422Returned when the pet data fails validation.
defaultReturned when an unexpected error occurs.

Error handling

A 400 is returned when the pet ID is invalid, a 404 when the pet is not found, and a 422 when validation fails. name and photoUrls are required, and status must be available, pending, or sold.