Schemas
This section documents the core data models used by the API.
Related endpoints:
Pet
Represents a pet resource as returned by the API.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
id |
string |
Yes | Unique identifier for the pet. |
name |
string |
Yes | Display name of the pet. |
tag |
string |
No | Optional tag/category for the pet (e.g., dog, cat). |
Example
{
"id": "pet_123",
"name": "Fido",
"tag": "dog"
}CreatePetRequest
Request body used to create a new pet.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
name |
string |
Yes | Name of the pet to create. |
tag |
string |
No | Optional tag/category for the pet. |
Example
{
"name": "Whiskers",
"tag": "cat"
}Notes
tagis optional on both models; omit it if you don’t need categorization.- The
idfield is required onPetobjects returned by the API, but is not provided inCreatePetRequest.