• Home
  • FAQ
  • Features
  • Docs
  • About
  • Pricing
Log In
Log InJoin Now

Create Records

Create pet profiles and people records with the PawPlacer API

Use POST /api/pets to create pet profiles and POST /api/people to create adopter or foster records from your own systems. Both endpoints validate required fields, enforce rate limits, and support idempotency keys for safe retries.

Request Overview

POST https://pawplacer.com/api/pets
x-api-key: YOUR_API_KEY
Content-Type: application/json
PropertyRequirement
Rate limit10 requests/hour
Authenticationx-api-key header
Body formatJSON

Required Fields

FieldAccepted values
nameAny non-empty string
speciesdog, cat, rabbit
age_categoryyoungest, young, adult, senior
sexmale, female, unknown
sizexSmall, small, medium, large, xLarge
statusYour custom status name or label (case-insensitive)
healthunknown, poor, good, great

If the provided status label does not exist, PawPlacer falls back to your default “available” status.

Optional Fields

CategoryFields
Identificationcustom_id, microchip_id
Visualsimage_urls (array of URLs), show_public (boolean)
Demographicsbreed (array), color (array), weight (string), coat_length
Datesintake_date, outcome_date, age_birthday (ISO 8601 strings)
Compatibilitygood_with, bad_with (values listed below)
Behaviortemperaments (values listed below), special_needs (array)
Notesdescription, status_change_notes
Administrationprimary_veterinarian_id (UUID), template_id (UUID)
Intake metadatacustom_status_id (UUID), location_found, reason_for_surrender
Financialadoption_fee (string or number)
Custom datacustom_field_data object keyed by field_key

Allowed Compatibility Values

activeLifestyle, cats, disabledMental, disabledPhysical, dogs, families, firstTimeOwners, frequentTravelers, kids, otherPets, outdoorsLiving, sedentaryLifestyle, seniors, smallApartments

Allowed Temperament Values

affectionate, aggressive, cuddly, curious, docile, energetic, fearful, gentle, independent, loyal, mischievous, moody, playful, protective, quiet, rough, shy, smart, social, stubborn, vocal

Custom Fields

  1. Call GET /api/pets/custom-fields.
  2. Use the field_key values returned (not the human-readable label).
  3. Provide values that match each field’s type (text, number, select, etc.).
  4. Invalid keys trigger a 400 response that includes a list of available fields.

Example Request

const response = await fetch('https://pawplacer.com/api/pets', {
  method: 'POST',
  headers: {
    'x-api-key': process.env.PAWPLACER_API_KEY,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    name: 'Max',
    species: 'dog',
    age_category: 'young',
    sex: 'male',
    size: 'medium',
    status: 'Available',
    health: 'good',
    show_public: true,
    breed: ['Labrador Retriever'],
    good_with: ['families', 'kids'],
    temperaments: ['playful', 'loyal'],
    adoption_fee: 250,
    custom_field_data: {
      favorite_toy: 'Tennis ball'
    }
  })
});

if (!response.ok) {
  throw await response.json();
}

const pet = await response.json();

Success Response

The endpoint returns the newly created pet with normalized data. Status values are resolved to their display label, and arrays are always present even when empty.

{
  "id": "d4738cf8-f31f-453d-a6c1-ba321a845c55",
  "name": "Max",
  "species": "dog",
  "breed": ["Labrador Retriever"],
  "color": [],
  "age_years": null,
  "age_months": null,
  "age_category": "young",
  "sex": "male",
  "size": "medium",
  "status": "Available",
  "health": "good",
  "spayed": false,
  "adoption_fee": "250",
  "microchip_id": null,
  "good_with": ["families", "kids"],
  "bad_with": [],
  "temperaments": ["playful", "loyal"],
  "image_urls": [],
  "coat_length": null,
  "custom_field_data": {
    "favorite_toy": "Tennis ball"
  },
  "custom_id": null,
  "intake_date": null,
  "outcome_date": null,
  "show_public": true,
  "special_needs": [],
  "status_change_notes": null,
  "weight": null,
  "created_at": "2025-07-29T13:34:20.242277+00:00",
  "updated_at": "2025-07-29T13:34:20.242277+00:00"
}

Idempotency

Use an Idempotency-Key header when your integration may retry the same create request. PawPlacer will replay the original successful response for the same key and payload, and it will reject the request with 409 idempotency_conflict if the same key is reused with a different body.

Error Responses

StatusReasonExample Payload
400Validation failure{ "error": "Validation failed: name - Required", "code": "validation_failed", "request_id": "..." }
400Malformed JSON{ "error": "Malformed JSON body", "code": "malformed_json", "request_id": "...", "hint": "Ensure body is valid JSON and header is application/json" }
400Unsupported content type{ "error": "Unsupported Content-Type. Use application/json for POST /api/pets.", "code": "unsupported_content_type", "request_id": "...", "hint": "Set header: Content-Type: application/json" }
401Missing or invalid API key{ "error": "API key required", "code": "api_key_required", "request_id": "..." }
403Read-only key used on a write endpoint{ "error": "This API key does not have write access. Use a write-enabled key for this operation.", "code": "insufficient_scope", "request_id": "..." }
405Empty body{ "error": "Empty request body. To list pets, use GET /api/pets. POST creates new pets.", "code": "method_not_allowed", "request_id": "..." }
409Reused Idempotency-Key with different payload{ "error": "This Idempotency-Key was already used with a different request payload.", "code": "idempotency_conflict", "request_id": "..." }
429Rate limit exceeded{ "error": "Rate limit exceeded. Maximum 10 writes per hour for this key.", "code": "rate_limited", "request_id": "..." }
500Unexpected server issue{ "error": "Something went wrong", "code": "internal_error", "request_id": "..." }

Retry only after resolving validation errors or waiting for the rate limit window to reset.

Best Practices

  • Convert numeric fields like adoption_fee to strings if your language does not preserve large numbers automatically.
  • Provide show_public: true when you want the pet to appear in public listings immediately.
  • Call GET /api/pets after creation if you rely on the list endpoint for displays; it reflects the new pet instantly.

POST /api/people – Create Adopter or Foster

POST https://pawplacer.com/api/people
x-api-key: YOUR_API_KEY
Content-Type: application/json
PropertyRequirement
Rate limit10 requests/hour
Authenticationx-api-key header (write scope)
Body formatJSON

Required Fields

FieldAccepted values
typeadopter or foster
nameAny non-empty string

Optional Fields

FieldTypeNotes
emailstringValidated email address
phonestringPhone number
addressstringMailing address
statusstringpending, active, training, inactive, denied, suspended, blocked. Defaults to pending.
status_change_notesstringNotes about the status
custom_field_dataobjectKeyed by field_key from GET /api/people/custom-fields
capacitynumberFoster capacity (integer, min 0)

Example Request

const response = await fetch('https://pawplacer.com/api/people', {
  method: 'POST',
  headers: {
    'x-api-key': process.env.PAWPLACER_API_KEY,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    type: 'adopter',
    name: 'Jane Smith',
    email: 'jane@example.com',
    phone: '555-0100',
    address: '123 Main St',
    custom_field_data: {
      has_yard: true
    }
  })
});

const adopter = await response.json();

Success Response

New records are created with status: "pending" by default. The response includes all person fields:

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "type": "adopter",
  "name": "Jane Smith",
  "email": "jane@example.com",
  "phone": "555-0100",
  "address": "123 Main St",
  "status": "pending",
  "status_change_notes": null,
  "custom_field_data": { "has_yard": true },
  "tags": [],
  "capacity": null,
  "created_at": "2026-04-10T10:00:00.000000+00:00",
  "updated_at": "2026-04-10T10:00:00.000000+00:00"
}

Idempotency

Use an Idempotency-Key header for safe retries, same behavior as POST /api/pets.

Error Responses

StatusReason
400Missing type or name, invalid email, or malformed body
401Missing or invalid API key
403Read-only key used on a write endpoint
409Idempotency key conflict
429Rate limit exceeded
PreviousGet DataNextDeveloper API

PawPlacer

© Copyright 2026 PawPlacer. All Rights Reserved.

Contact
  • Email
About
  • About Us
  • Funding Philosophy
  • Careers
  • FAQ
  • Pricing
  • Changelog
Legal
  • Terms of Service
  • Privacy Policy
  • Cookie Policy