Skip to main content

Integrations

Connect PawPlacer to websites, pet listing services, PetLink, and custom software

In this guide

Key sections from this documentation page.

PawPlacer can publish selected data on another website, synchronize listings with Petfinder and Adopt-a-Pet, register microchips through PetLink, or provide server-side access through the SDK and public API.

Website Widgets

Widgets are the fastest way to add PawPlacer to an existing website. Choose a full public profile, a pet gallery, or an adopter, foster, volunteer, surrender, or donor form. PawPlacer supplies the HTML and JavaScript snippet, responsive iframe behavior, and real preview.

You need permission to add custom HTML and JavaScript to the destination site, and the organization's PawPlacer public profile must be visible.

Petfinder

Petfinder Sync sends eligible public pet listings through Petfinder's FTP import. The settings page provides credential setup, a validation preview, inline issue links, manual synchronization, and optional scheduled synchronization.

You need an active Petfinder organization and FTP credentials issued for the integration.

Adopt-a-Pet

Adopt-a-Pet Sync publishes PawPlacer pets through Adopt-a-Pet AutoUpload. The shared Listing Integrations page provides FTP credential setup, provider-specific status mapping, validation, manual synchronization, and optional scheduled synchronization.

You need an Adopt-a-Pet Shelter Zone account with AutoUpload enabled and the FTP credentials shown under Manage My AutoUpload Account.

GetBuddy

The Now connected with GetBuddy card on Settings > Listing Integrations explains that your adoptable pets are shared with GetBuddy automatically, based on your public visibility settings; there is nothing to connect. GetBuddy uses your existing PawPlacer adoption forms, and applications come straight into PawPlacer. Choose Manage public visibility to review those settings.

PetLink Microchip Registry connects a PetLink Animal Professional account. Teams can draft a registration, validate the chip and owner, handle existing-registration transfers, submit to PetLink, and review prepaid or payment metadata returned by PetLink.

You need a PetLink account with API access. If PetLink reports that payment is due, review the returned payment details after submission.

SDK and Public API

The JavaScript SDK is the preferred path for JavaScript and TypeScript. The public API supports raw HTTP and other runtimes.

Supported data includes:

  • Account pets, individual pets, and pet custom-field metadata through a scoped API key
  • Adopters, fosters, surrenders, volunteers, and their custom-field metadata
  • Pet creation and updates
  • Adopter, foster, surrender, and volunteer creation
  • Adoption fee rules and contract content

Create a Read only key for trusted listing backends and a separate Write + read key for trusted server-side write jobs. API reads return account-scoped records, so apply public eligibility rules before publishing them. Never place a PawPlacer API key in browser code.

Choose a Path

  • Use Widgets when you want PawPlacer to render public content and forms.
  • Use Petfinder when Petfinder should receive your PawPlacer listings.
  • Use Adopt-a-Pet when Adopt-a-Pet AutoUpload should receive your PawPlacer listings.
  • Use PetLink for microchip registration and transfer workflows.
  • Use the SDK for a typed server-side JavaScript or TypeScript integration.
  • Use the public API for direct HTTP, generated clients, or non-JavaScript systems.

Keep reading

Move through the documentation in order.