Swagger Petstore - OpenAPI 3.0
PUT/pet

Replace a pet in the store

Replaces an existing pet record in the store. Provide name and photoUrls in the pet representation; status, when supplied, must be available, pending, or sold. The request accepts JSON, XML, or URL-encoded form data.

6 body fields

Pet details to replace the existing store record. The body can be sent as JSON, XML, or URL-encoded form data; name and photoUrls are required.

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

5 status codes
200Returns the updated pet object, including its identifier, name, photo URLs, and any supplied category, tags, and status.
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 to update is not found.
422Returned when the pet payload fails validation.
defaultUnexpected error

Error handling

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