All writing

Automating Real Estate Listings with Terraform: Introducing the Immobilienscout24 Provider

4 min readimmobilienscout24immoscoutopen-sourceterraformterraform-provider

Originally published on Medium.

Introduction#

As someone who has spent over 15 years designing, building, and securing cloud infrastructure, automation is in my DNA. My career has spanned fintech, mobility, gaming, and health tech, leading high-performing engineering teams and optimizing complex systems for scale, resilience, and cost. At every step, Infrastructure as Code (IaC) has been a cornerstone of delivering reliable, repeatable results.

I guess the world of real estate lags behind. While looking for an apartment in Berlin — a task not for the faint-hearted — I noticed a recurring thing: some ads are available for a very short time, so publishing or updating real estate listings must be tedious for landlords and property managers. It looks like a manual process, even for large-scale businesses, and updating content must be a nightmare. That's where the idea for an open-source Immobilienscout24 Terraform provider was born.

Why I built the Immobilienscout24 Terraform provider#

Immobilienscout24 is one of Germany's most popular real estate portals. Yet its integration with cloud-native workflows is almost non-existent, with few notable exceptions like GetTheFlat (and even they are short on features).

My motivation was simple:

  • Reduce friction for Ops teams managing real estate portfolios.

  • Empower "automation-minded" companies to publish listings just like they should automate their cloud infrastructure, with version control and CI/CD.

  • Encourage the real estate ecosystem to embrace open source and modern best practices.

I believe any repetitive process, be it spinning up servers or publishing apartments, deserves automation.

Who is this for?#

This provider is for:

  • Real estate agencies, SaaS startups, and proptech (no idea if the term exists) teams who want to automate listing creation and maintain parity across multiple platforms — perhaps, in the future, with a multi-provider Terraform module.

  • Cloud engineers or tech consultants working for real estate clients who need auditability, rollback, and repeatability in listings.

  • Open-source enthusiasts keen to bridge traditional industries with the power of infrastructure automation.

If you've ever thought, "Why am I still clicking through a portal to publish properties?"… this is for you.

How it works#

The Immobilienscout24 Terraform provider is an MVP that lets you insert a new real estate listing using the official API. It uses OAuth1 authentication and is built with the modern Terraform Plugin Framework.

Usage example#

I want to clarify that this process may change once the provider is built and published automatically. With that said, after building the provider from source, you can automate a listing with just a few lines of code:

hcl
provider "immobilienscout24" {
  consumer_key        = "YOUR_CONSUMER_KEY"
  consumer_secret     = "YOUR_CONSUMER_SECRET"
  access_token        = "YOUR_ACCESS_TOKEN"
  access_token_secret = "YOUR_ACCESS_TOKEN_SECRET"
}

resource "immobilienscout24_realestate" "listing" {
  title            = "Modern Apartment"
  description_note = "Listed via Terraform!"
  street           = "Sample Street"
  house_number     = "5A"
  postcode         = "10115"
  city             = "Berlin"
}

Running terraform apply will create a new listing in your Immobilienscout24 account (using their sandbox API, for now).

The roadblocks: Getting access to the API#

Kickstarting the provider build has been great, and a big part of it was the official documentation on ImmoScout's API and the amazing official Terraform docs.

The real challenge? Getting access to the Immobilienscout24 API. When I reached out for API credentials, I was met with a series of questions about open source, Terraform, and usage intent. For the most part, normal questions — but I did get the feeling that the support team hadn't engaged with infrastructure-as-code tools before or consulted with their internal development teams.

They also clarified that API access is not free, creating another barrier for innovators and community projects — and therefore blocking me from actually testing the provider in real life.

It's a reminder that while technology moves fast, large organizations, startups, and industry leaders can take time to catch up with the open-source and automation movements. I hope that, by releasing this provider, I can spark the conversation, show the real value of the open-source community, and encourage platforms like Immobilienscout24 to invest more in accessible developer tooling.

What's next: Expanding the provider#

This is just the beginning! I plan to add:

  • Read, update, and delete support for real estate listings.

  • Additional resource types, such as data sources for listing images, or perhaps even agent management.

  • Production-grade features (or as production-grade as possible): robust error handling, test coverage, and documentation.

  • Community feedback: if you're using this or want to see new features, open an issue or PR.

As a longtime advocate for open source and automation in every industry, I'm committed to empowering teams to move faster, with less friction — even in traditional sectors like real estate.

Final thoughts#

If you're a developer, NinjaOps engineer, or even a business leader, I encourage you to try the provider, share feedback, or contribute with an issue or a PR.

Let's bring the power of open source and automation to every part of the stack, even the ones that still think in PDFs and portals.

Get the code: github.com/agusgonzaleznic/terraform-provider-immobilienscout24

Let's automate real estate together!

Agustin Gonzalez Nicolini

Coaching for engineering leaders, from someone who has held the pager.

Based in Berlin, from Haedo • Coaching globally

Quick Links

  • Blog

Connect

© 2026 Agustin Gonzalez Nicolini. All rights reserved.