Recipes

The quickstart teaches one happy path. Recipes teach the next things you'll actually build. Each one is a single task — problem statement, minimal code you can paste, why it works, and what to watch out for. Every recipe runs againstapi.propsocket.io with a ps_test_ key and the real CDM entities — nothing invented.

Heads up. The webhook-based recipes (listen for new leases, dedupe webhooks, reconcile after an outage) require webhooks, which are on the Scale plan and above (Scale and Enterprise). The API- and CSV-based recipes work on every plan — see pricing.

Listen for new leasesWire the LEASE_SIGNED webhook, verify it, persist the lease, and emit a downstream event.Export units for one property nightly to CSVA cron job that pages /v1/units?property_id=… and writes a stable CSV. No SFTP feature required.Backfill a warehouse after downtimePage every entity by created_at:asc and upsert idempotently on x_id. Safe to re-run.Dedupe webhooks idempotentlyUse the event id (a ULID) as the dedupe key so at-least-once delivery is exactly-once for you.Reconcile after a webhook outageWhen your receiver was down, replay from the dashboard or sweep updated_after to catch up.

Searched for a recipe and didn't find it? Tell us what you're building — gaps here become the next recipes.