Turns structured property data into a finished listing - as a PDF and as a
web view - and publishes it to the channels you choose.
A listing always references exactly one property from Property
Management. Standalone listings without a property are intentionally
not supported, so mandatory disclosures and history stay maintained in a
single place.
Workflow
POST /listingsstarts the generation. The response carriesstatus: "in_progress".- Once the document is ready, the status changes to
completed. We recommend
subscribing to thelisting.completedevent instead of polling. GET /listings/{listingId}/pdfreturns the document.POST /listings/{listingId}/publishputs it live on the chosen channels.
Mandatory disclosures
Before publication the API checks the disclosures required by law - most
importantly the energy-certificate figures and the commission statement.
If something is missing, the API responds with 422 and
code: "mandatory_disclosure_missing".
- Server 1:https://api.realestateagency.example/v1
Production
- Server 2:https://sandbox.api.realestateagency.example/v1
Sandbox - data is reset nightly
apiKey (apiKey)
Every call carries an API key in the apikey header. You generate the
key in the Real Estate portal under “My Apps”; it’s shown exactly once.
Each key has the scopes it’s allowed to use attached to it. If one is
missing, the API responds with 403 and code: "scope_missing"; the
missing scope is in details[].field.
For demonstration purposes only License