Partners & developers
Multi-location API from day one — so we never bolt it on later.
Property managers, venue groups, and companies with several sites use one Organization with many Locations and Listings. Authenticate with a live API key. Platform fee: 15% (founding rates lockable).
Org → Location → Listing
Same hierarchy for a single homeowner or a 40-site operator.
API keys
dy_live_… keys, hashed at rest, Bearer or X-Api-Key.
Web + future apps
Same /api/v1 for the site and later iOS/Android.
Public & partner endpoints (live)
GET /api/v1/healthService status, fee bps, inventory counts
POST /api/v1/leadsMarketing / partner inquiry leads
GET /api/v1/listingsPublic published + preview catalog
POST /api/v1/orgsCreate organization (bootstrap key)
GET|POST .../orgs/:id/locationsMulti-site property locations
GET|POST .../orgs/:id/listingsListings under each location
Try health: /api/v1/health · Docs live in
PLANNING/openapi/openapi-v1.yaml and PLANNING/18-MULTI-ORG-AND-PARTNER-API.mdExample: create org + location + listing
# 1) Bootstrap org (server bootstrap key)
curl -X POST https://dashyards.com/api/v1/orgs \
-H "Content-Type: application/json" \
-H "X-DashYards-Bootstrap-Key: $DASHYARDS_BOOTSTRAP_KEY" \
-d '{"name":"Desert Event Venues LLC","email":"[email protected]","type":"venue_group","createApiKey":true,"foundingHost":true}'
# 2) Add a location (use returned API key)
curl -X POST https://dashyards.com/api/v1/orgs/{orgId}/locations \
-H "Authorization: Bearer dy_live_..." \
-H "Content-Type: application/json" \
-d '{"name":"Lancaster Pool Estate","city":"Lancaster","state":"CA"}'
# 3) Create a listing at that location
curl -X POST https://dashyards.com/api/v1/orgs/{orgId}/listings \
-H "Authorization: Bearer dy_live_..." \
-H "Content-Type: application/json" \
-d '{"locationId":"loc_...","title":"Resort Pool Day Venue","dayRateCents":20000,"maxGuests":40,"restroomAccess":true,"parkingSpots":8}'Request partner API access
Tell us how many locations you manage. We will issue bootstrap onboarding and API keys for production.
Solo host? Use host onboarding →