| 开发者 | wohno |
|---|---|
| 更新时间 | 2026年6月18日 14:05 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
search="1".[wohno_listing id="…"].wohno).[wohno_listings city="Köln" rooms_min="2" rent_max="1200" limit="9" columns="3"]
sk_…) with
the listings:read scope.[wohno_listings] shortcode on a page.Yes. You create an API key with the listings:read scope in the Wohno dashboard.
No. The detail page and the application run first-party on wohno.de. No applicant data is created on your site.
Yes, the overview list is rendered as real HTML. The individual detail pages live canonically on wohno.de.
Yes. The key is stored server-side only (encrypted where the server provides
openssl) and sent only over HTTPS in the X-API-Key header — never in the
browser, never in the page source, never in logs.
No. Discrete listings are intentionally not delivered by the API.
[wohno_listing id="…"] shortcode is generated — no need to
look up the ID.[wohno_listings …] shortcode.search="1"): visitors can
filter your portfolio by text, city, type, rooms, rent and WBS — server-side
and SEO-friendly, working with every layout and "load more".layout="cards") and list (layout="list") next to
grid and map; refreshed card design closer to wohno.de.wp_set_script_translations).[wohno_listing id="…"] and a dedicated block.layout="map") with Leaflet + OpenStreetMap (no API key).