Rentology Resources

How to disable an API feed for a property listing (without breaking your marketing)

By Ingo Schaer, founder of Rentology · Updated 2026

Person working on a laptop at a wooden desk Photo: @microsoftcopilot on Unsplash

You can disable a property’s API feed by turning it off at the source system that publishes the feed, by changing your broker/MLS syndication settings (ListHub or Trestle), or by pausing the listing on each portal that consumes the feed. Pick the narrowest switch that solves the problem, document it, and confirm on the sites where your listings appear before you walk away.

What is an API feed in this context?

An “API feed” is the data pipeline that pushes your listing details, photos, pricing and status from your source system (property management software, MLS, or vendor) to consumer sites and partner portals. That feed can flow through:

  • Your PMS or channel manager (for STR/MTR) to booking sites and rental portals.
  • Your broker/MLS syndication hub (for LTR) to real-estate portals (e.g., via ListHub or CoreLogic Trestle).
  • A custom vendor feed to a single portal or network.

Disabling the feed can mean different scopes of change: stopping one listing on one portal, pausing a whole portal for all listings, or killing the feed at the root so nothing publishes anywhere from that source.

What are your practical options to disable a listing feed?

There are three main levers. Use the one that matches your risk, timing and scope.

  • Source-level switch (PMS/channel manager or MLS entry): turning the listing to “unavailable/offline” or excluding it from export stops it before it syndicates anywhere. This is the safest for accuracy.
  • Broker/MLS-level syndication controls: use your syndication hub to opt out of specific portals or all distribution. ListHub lets brokers enable/disable individual “publishers” in the broker dashboard under Publishers → My Publishers source. CoreLogic Trestle provides “Syndication Management” to set opt‑in/opt‑out per third‑party portal source.
  • Portal-level pause/unpublish: log into the portal account and unpublish the unit. This can be fastest for a single site but leaves copies live elsewhere if other portals still receive the feed.

How do MLS/broker syndication hubs handle opt-outs?

  • ListHub: Brokers can toggle distribution to each publisher at any time from the broker dashboard (Publishers → My Publishers). ListHub also announces new publishers to MLSs and holds them for a five‑business‑day review before brokers see them, which is relevant when you evaluate future distribution changes source.
  • CoreLogic Trestle: Brokers can use “Syndication Management” to set opt‑in status for each third‑party portal, and recent materials highlight improved management of credentials and UI for these choices source. Some MLSs note trade‑offs: if you opt out of IDX/data‑feed sharing, you lose the ability to display other brokers’ IDX listings on your own site source.

Those controls are broker-level decisions. Confirm your role and access; some Trestle configurations restrict access to designated broker roles source.

What about Zillow Rentals and similar networks?

Zillow Rentals’ policy says the feed provider “will provide to Zillow Rentals all rental listings made available through its data feed,” and multifamily listings are expected to remain in the feed with a representative floor plan even when a specific unit is unavailable source. The practical takeaway: turning off a single unit’s ad can require you to change the status at the source (PMS/feed) rather than expect portal-side suppression to stick. If your vendor aggregates units into a community feed, coordinate with the vendor on the correct field to signal “unavailable” without violating feed obligations.

Step-by-step: how to disable an API feed for a listing

Use the narrowest step that achieves your goal. Start at the source; escalate outward only if needed.

  1. Identify the source of truth
  • Is the listing coming from your PMS/channel manager, your MLS, or a custom vendor feed?
  • Audit where the listing currently appears (your company site, portals, booking channels). Keep a short list you can re-check.
  1. Turn off at the source system (preferred)
  • For PMS/channel managers: set the listing to “unavailable,” “snoozed,” or exclude from export. That prevents downstream updates everywhere that consumes the feed.
  • For MLS entries: change status to the correct off‑market or unavailable code per MLS rules, which your syndication hubs will then honor.
  1. Adjust broker/MLS syndication settings if the issue is portal-specific
  • ListHub: in the broker dashboard, go to Publishers → My Publishers and disable the target publisher source.
  • Trestle: use “Syndication Management” and set the portal’s opt‑in to off for the feed in question source.
  • Note the IDX trade‑off: opting out of IDX sharing can remove your ability to show IDX listings on your own site source.
  1. Portal-level contingency
  • If you need the fastest takedown on one site, unpublish the listing in that portal’s owner/partner dashboard. Then fix the source so it does not republish on the next sync.
  1. Confirm and document
  • Wait for the next feed cycle and verify on each target site. Take screenshots and record the timestamp and person responsible.
  • For multifamily feeds to Zillow Rentals, make sure your source vendor sends the correct structure (e.g., community with representative floor plan) rather than removing the whole feed if only a unit is unavailable source.

Quick comparison: which lever should you pull?

Approach Scope Speed Risk of re-publish When to use
Turn off in PMS/MLS (source) Stops all downstream exports for that listing Moderate (depends on next sync) Low You want consistency across all portals
Broker/MLS syndication (ListHub/Trestle) Stops a portal or network for all your listings Moderate Medium (other portals might still show) You want to halt a specific site without touching listing status
Portal unpublish Single site only Fast High (source can re-enable on next sync) Emergency or one-off takedown

Example: deciding the narrowest switch

Example: You have a listing live on four portals through your MLS syndication. You need it off only on one site because of a compliance concern. If you disable the one publisher in ListHub/Trestle, you remove exposure on 1 of 4 sites. That is a 75% reduction in that portal’s exposure relative to your total portal mix for this listing, without changing its MLS status. Next, you confirm that the remaining three portals still display correctly after the next sync.

How do ListHub and Trestle handle changes over time?

  • ListHub introduces new publishers to MLSs and holds them for a five‑business‑day review before brokers can opt them in, which helps avoid surprise distribution expansion source.
  • Trestle’s “Syndication Management” lets you change opt‑in status per portal and includes account/credential controls. Access can be limited by broker role, so coordinate with the designated broker if you lack permissions source.
  • Some MLSs warn that opting out of IDX/data‑feed programs has side effects for your own site’s listing display source. Plan for that before you flip a global switch.

How do portal policies change what you should do?

Zillow Rentals expects the feed provider to include all rental listings that the provider makes available through its feed, and multifamily communities should remain in the feed with a representative floor plan even when a unit is unavailable source. That means:

  • If you are advertising a community with unit‑type plans, unpublishing one unit on the portal could be undone by the next feed cycle unless you align the source data with policy.
  • If you only need to prevent inquiries for a temporarily unavailable unit, the cleanest path is to set the correct status at the source and keep the community structure intact.

Where sources differ: MLSs and portals vary in how quickly changes propagate and how strictly they enforce structural feed rules. ListHub and Trestle document broker controls, while portal policies add constraints for how inventory types are represented. Always read your MLS rules and the portal’s feed specs in addition to the general steps here.

What goes wrong in practice

Operator reality often differs from the clean diagrams:

  • The “wrong” source of truth: A teammate hand‑created a listing on a portal while the PMS still exports it. You unpublish on the portal, and it returns at the next sync. Fix the source first.
  • Multiple feeds for the same property: One MLS feed and one PMS feed both publish similar listings to the same site under different accounts. You disable one and the other stays live. Inventory audit solves this.
  • Role/permission roadblocks: Only the designated broker can change Trestle settings. You spend a full day routing an access request. Anticipate who must click the button.
  • Stale caches: Even after disabling, a portal’s cache or CDN can show the page for a while. Keep your confirmation window open long enough to see the status flip.
  • Multifamily nuance: A community feed to a rental network expects a representative plan image and availability pattern. Removing the unit incorrectly triggers a data‑quality warning. Coordinate with your vendor per the network’s policy source.

How do I choose between source, syndication, and portal controls?

Ask three questions:

  • Is this temporary or permanent? For temporary changes, a portal unpublish can be enough if you also set the correct source status to prevent re‑posts.
  • Is the problem one site or many? If it is one site, change syndication for that publisher. If it is systemic (wrong price/details everywhere), fix the source.
  • Do I need broker approval? If your MLS data powers your feed, changes inside Trestle/ListHub can require broker‑level action. Plan your internal routing.

Checklist before you press “disable”

  • Inventory map: List every site where the listing is live.
  • Source status: Set the listing to the correct “off” state in the PMS/MLS.
  • Syndication scope: Decide if you also need broker/MLS changes.
  • Portal exceptions: Read the destination portal’s feed policy for your asset type policy example.
  • Evidence: Take before/after screenshots with timestamps.

Can software help you keep distribution under control?

If you manage STR/MTR/LTR in one workflow, centralizing listing status and owner reporting reduces feed mistakes. Some platforms focus on operations while connecting to channel managers for distribution. Example: an operator platform that connects to systems like OwnerRez, Hospitable and Beds24 for bookings and guest messages can keep messaging and statements in one place and leave distribution to the connected channel managers. If you want a single pane for STR/MTR/LTR ops and owner statements while keeping your existing channel tools, see an overview of mid‑term features and owner statement workflows here:

Note: If you evaluate options like Rentology, its approach is to connect to OwnerRez, Hospitable and Beds24 for bookings and guest messages instead of replacing them; Airbnb and Vrbo traffic flows through those systems according to that setup. This keeps distribution switches closer to your channel manager while your operations and statements run in the operator platform.

Key takeaways

  • Brokers can toggle portal distribution in ListHub under Publishers → My Publishers source.
  • CoreLogic Trestle provides per‑portal opt‑in/opt‑out controls via “Syndication Management” source.
  • Opting out of IDX/data‑feed programs can stop you from displaying IDX listings on your own site source.
  • Zillow Rentals expects feed providers to include all rentals made available through the feed, and multifamily listings should remain represented even when individual units are unavailable source.
  • The safest way to prevent re‑publishing is to disable at the source and then align syndication and portal settings.

Frequently asked operator questions

How can I disable an API feed for a property listing without affecting other properties?

Turn the listing off at the source for that one property (PMS/MLS status or export exclusion). If the problem is only on one portal, use your broker/MLS hub to opt out of that specific publisher (ListHub/Trestle) and leave others untouched ListHub Trestle.

Will disabling IDX or a data feed hurt my website?

It can. Some MLSs warn that opting out of IDX/data‑feed programs means you cannot display other brokers’ IDX listings on your own site, which is a real trade‑off source. Consider a portal‑specific change first.

Why does my listing keep reappearing after I unpublish it on a portal?

The source system still sends it. On the next sync, the portal receives the live status and republishes. Fix the listing status at the source, then keep the portal unpublished until the next feed cycle completes.

What is different about multifamily feeds to rental networks like Zillow Rentals?

Zillow Rentals expects the feed provider to continue sending community listings and use a representative floor plan even when a unit is unavailable source. Coordinate with your feed vendor so your change reflects that structure rather than deleting the entire feed.

Sources

Loading…