Helipaddy sites vs Kelley Blue Book

Helipaddy's Partner API returns nearby helicopter, EVTOL, and drone landing sites — hotels, aerodromes, pubs, and B&Bs with helipads — as JSON, gated to a per-partner category allow-list. A live GET and OPTIONS preflight against its real API host, helipaddy.com/wp-json/hp-partner/v1/sites, both echoed access-control-allow-origin back with the request Origin, resolving the stored "unknown" cors to "yes"; the GET returned a "hp_partner_api_invalid_key" 401 error, reconfirming auth "API Key" over HTTPS. Partner tokens are issued manually via WhatsApp/email under a negotiated agreement with no public self-serve tier — paid.

Kelley Blue Book's Cox Automotive-run API program (IDWS, Advertising Data, Instant Cash Offer, and Batch VIN) provides vehicle valuation, pricing, and configuration data behind an approval-gated API key, per developer.kbb.com's own access instructions. Its legacy Swagger doc-viewer content pages (/content/data/*.html) now 404 into the site's SPA shell — orphaned — but the surrounding portal, the key-request process, and Cox Automotive's successor developer platforms (developer.coxautoinc.com, coxautoinc.mashery.com) all remain live over HTTPS, confirming https true and that the program has moved rather than gone dead; cors could not be re-probed live since no public endpoint or key is available. Access requires Cox Automotive approval with no public self-serve signup — paid.