The ImmoScout24 API lets your software publish listings to ImmobilienScout24 automatically: you create the property with one REST call, upload each photo as a separate attachment, then publish the property to channel 10000. You need an ImmobilienScout24 business account, an API key and user consent through OAuth 1.0a. There is no FTP route for this, because ImmobilienScout24's own FAQ says listing data is accepted only through the REST API.
Which ImmoScout24 API you actually need
ImmobilienScout24, Germany's largest property portal, runs several APIs: search, geo services, construction financing and more. If you want to publish listings, the one that matters is the Import/Export API, which the terms of use call the Real Estate Listing API. It creates, changes, deletes and publishes real estate objects, and it reports on objects that are already live.
The detail that trips up most first integrations is that a real estate object holds only the property data. The contact person, the photos and documents, and the publication itself are separate resources with their own endpoints. A live listing is the result of a short sequence of calls, not a single request. Once you see it that way, most error messages start to make sense.
If you also feed other German portals through OpenImmo files, our comparison of OpenImmo and the ImmoScout24 API covers that choice. This post stays with ImmobilienScout24 and walks through the actual workflow.
What you need before the first call
Most of the setup is paperwork rather than code. This is what ImmobilienScout24's developer documentation asks for, as checked on 27 October 2026.
| Requirement | What the documentation says |
|---|---|
| Account | Non-business accounts cannot be used for API access. You create a business account first (client credentials). |
| API key | Keys and secrets exist for the sandbox, production or both, and they are shown only once. The use case Kundenwebsite / Immobilienverwaltungssoftware gives the key the permissions to send and retrieve your own objects. |
| Authentication | OAuth 1.0a. Working with a user's listings needs the three-legged flow, and each access token belongs to exactly one user (three-legged OAuth). |
| Test environment | The sandbox is a clone of production with its own anonymous database. Nothing is booked and no emails go out. |
| Cost | The live API is paid. The monthly fee follows the average number of API calls over the previous three months, priced from a volume list, plus VAT (terms of use, section 3, German). |
| Quota | The customer account needs a quota (Kontingent) for automatic publishing. Without one, the API answers No contingent available (CRM user FAQ, German). |
Treat the sandbox as disposable. ImmobilienScout24 deploys its latest release there every week and warns that test data, and even the sandbox key, can be lost. Write tests that can rebuild their own data from scratch, or a routine sandbox deployment will break them for you.
The publishing workflow, step by step
The real estate insertion tutorial lays out the order. In short:
- Create the object. POST to /offer/v1.0/user/me/realestate with the type (for example apartmentRent or apartmentBuy), title, address, price and area. The response returns the Scout object ID. Put your own reference in externalId (up to 50 characters) and you can address the object later with the prefix ext- instead of the Scout ID.
- Upload photos and documents. Each attachment is its own multipart request against an object that already exists. You cannot create the object and an attachment in the same request (insert an attachment).
- Link a contact. Optional. Reference a contact created through the contact resource; if you leave it out, ImmobilienScout24 uses the provider's default contact address.
- Publish. POST to /offer/v1.0/publish with the object ID and the channel: 10000 is ImmobilienScout24.de, 10001 is the customer's own homepage (publish).
Two rules from the docs are worth taping to the monitor. Send publish requests one after another, not in parallel, because every request checks the quota and parallel calls can fail. And do not send date fields with a GMT offset: the API ignores the whole field.
Updates, photos and taking a listing down
Publishing once is the easy part. A listing only counts as automated when price changes, new photos and withdrawals also run without anyone logging in to the portal.
| Task | Call | What to watch |
|---|---|---|
| Change a listing | PUT on the object | Send every attribute, even if only one changed, or the API cannot tell a missing field from a cleared one. The property type cannot change; create a new object instead. |
| Photos | Attachments per object | Up to 150 pictures or PDFs and up to 150 links per object, files up to 50 MB, videos up to 1 GB. Documents are scanned for malware and must not be password protected. |
| Withdraw | DELETE on the publication | One request per publication, for example ID 58850320_10000. Any OnTop placement on that listing is deactivated with it. |
| Delete the object | DELETE on the object | ImmobilienScout24 recommends deactivating objects rather than deleting them. |
The full-payload rule on PUT causes the most quiet damage. An integration that sends only the new rent can blank out other fields. If your system always sends the complete object from one property record, the problem never comes up.
Errors you will meet
The developer and CRM user FAQs list the messages that come up most. The ones we would plan for:
- MANDATORY_FIELD_EMPTY: a required field is missing. Living space, for example, may be neither empty nor 0.
- Energy certificate errors: the API validates energy fields against a matrix of certificate date, certificate type and property type, and answers _NOT_VALID_FOR_THIS_CERTIFICATE when a field does not fit. The field energyCertificateAvailability (AVAILABLE, NOT_AVAILABLE_YET, NOT_REQUIRED) switches that validation on or off (energy certificates).
- No contingent available: the account has no publishing quota left.
- 429 Too Many Requests: the rate limit is 2,000 requests per minute per API key, and the Retry-After header tells you how long to wait.
One thing the import side does not do is return inquiries. According to the developer FAQ, ImmobilienScout24 emails each contact request to the provider and reports the number of requests in the ScoutReport.
Build it yourself, or use software that already does
The API is well documented, and the first sandbox listing is rarely the hard part. The ongoing work is the part people underestimate: OAuth tokens per user, one upload per photo, publishes in sequence, retries when a call fails, complete payloads on every change, and energy fields that change with the certificate. Then there is the question of where the property data lives. If the listing is typed into one tool and the lettable area is maintained in another, you are still keying the same facts twice.
REPM talks to ImmobilienScout24 through the official IS24 REST API, against the sandbox or the production endpoint. One click on Publish in the ListingCockpit creates the publication and a sync job, and a durable outbox delivers it with the states Queued, Processing, Succeeded or Failed. A failed job shows the portal's error text and runs again with one click, and after a successful publish the expose link comes back to the listing. You set up the connection in the Portal Hub (connection check, OAuth certification, an active switch per portal), and the credentials sit in Azure Key Vault. The ImmobilienScout24 integration page has the details.
Summary
Automatic publishing through the ImmoScout24 API works well once you have a business account, OAuth 1.0a, a quota and the calls in the right order. It takes the least effort when the property data is maintained in one place and sent complete from there. To watch a listing go from a property record to the sandbox and back with its portal link, request a demo.