REPM talks to ImmobilienScout24 through the official IS24 REST API. One click on Publish in the ListingCockpit creates the publication and a sync job, a durable outbox delivers it, and the expose link comes back to the listing.
Publishing is controlled from the ListingCockpit on the property or listing record. Everything after the click is handled for you, and everything that happens stays visible.
Hit Publish in the ListingCockpit and REPM creates the publication and a sync job for ImmobilienScout24. No export files, no second tool.
Every job runs through a durable outbox: Queued, Processing, Succeeded or Failed. A failed job shows the portal's error text and runs again with one click.
After a successful publish the listing carries the IS24 expose link, and the publication shows Published with the portal URL.
Pick a view. The diagrams show the path a listing takes from REPM to the portal.
From the click in the ListingCockpit to the live listing: REPM creates the publication and a sync job, the outbox worker delivers it to the official IS24 REST API, and the expose link comes back.
Every sync job is durable and visible: Queued, Processing, then Succeeded with the portal URL or Failed with the portal's error text and a one-click retry.
The connection per portal lives in the Portal Hub in the Settings area: connection check, OAuth certification with ImmobilienScout24, the active toggle and the job log.
The Portal Hub in the Settings area, under Integrations, manages the connection per portal.
Verify credentials and reachability against the sandbox or production endpoint before anything is published.
Certify the connection with ImmobilienScout24 in the authorize-and-verify flow agents already know: sign in at the portal, grant access, verify in REPM.
Switch the portal on or off per connection and follow every sync job in the log, with state and result.
The outbox is durable: a job survives restarts and stays visible until it has succeeded.
Test against the IS24 sandbox, go live on production, and keep credentials where they belong.
Yes. REPM talks to ImmobilienScout24 through the official IS24 REST API, against the sandbox or the production endpoint.
In the Portal Hub in the Settings area, under Integrations: run the connection check, certify the connection with ImmobilienScout24 via OAuth, and switch the portal to active.
The sync job shows Failed with the error text the portal returned, and you retry it with one click. The outbox is durable, so no job is lost.
In Azure Key Vault, never in the app database.
We will connect the sandbox, publish a listing from the ListingCockpit and follow the job through to the portal URL, on your data.
Request a demo