Guidelines, changes and support

#Display rules

They apply to the widget, the API, feeds and the RESO Web API.

1. Credit the listing agent. On every other agent's listing show their name and, if any, their agency (agent.name, agency.name), and link to the listing page (url). The widget does it automatically ("Listed by…").
2. Fresh data. Cache for at most 12 hours and remove whatever is no longer published. Use updated_since (API) or ModificationTimestamp (RESO) to sync.
3. No scraping. Use the API, feeds or widget; do not download multilistado.mx pages automatically. Respect the rate limits.
4. Respect exclusions. Never show a listing the API does not return to you: those whose owner marked "not authorized on other agents' sites" (idx_opt_out) and licensed imports from other MLSs are already excluded. Do not obtain them any other way.
5. Location and privacy. Use coordinates as delivered (approximate unless location.exact: true); do not try to infer the exact address. Do not publish buyer or owner data.
6. No public commissions. Shared commissions are agent-to-agent information and are not exposed; do not publish them even if you know them.
7. Content as is. You may format and translate, but do not change prices, sizes or features. If you offer machine translation, say so.
8. Leads. Inquiries about other agents' listings received through your site are handled in cooperation with the listing agent (Multilistado is a cooperation network of licensed agents). Every showing requires a verified buyer ID.
9. Brand. You may say "Listings from Multilistado" and link to multilistado.mx; do not imply you are Multilistado or use its logo as your own.

Breaches can lead to revoked keys or widgets. Use is subject to the Terms and the Privacy notice.

#Support

• Email: contacto@multilistado.mx (include the URL you call, the time and the response; never send your full API key — the pbm_xxxxxxxx prefix is enough).
• US MLSs, brokers and vendors: partner program.
• Open source (AGPL-3.0): github.com/probienesmexico.

#Versions and compatibility

• /api/v1, the widget and webhooks are stable: we only add optional fields, parameters and events. Ignore fields you do not know.
• A breaking change would ship as a new version (/api/v2) and the old one would be kept for at least 12 months, announced on this page.
• The OpenAPI description (/api/v1/openapi.json) states its version in info.version.
• /api/app/v1 is internal to the iPhone app: not supported for third parties.

#Changelog

#2026-09-30

• New developer center at /developers (Spanish and English), with guides for WordPress, Wix, Squarespace, GoDaddy, Shopify, Webflow, Google Sites and Blogger, a snippet builder and an interactive reference.
• OpenAPI 1.1.0: complete, valid description (listing, lead, error, rate-limit and pagination schemas).
• API: GET /properties and GET /properties/{id} no longer return idx_opt_out listings or test accounts to other keys (they did before; now consistent with the widget and websites).
• API: GET /leads and POST /leads return a fixed list of documented fields (no internal columns).
• API: POST /properties with a repeated external_id returns 409 conflict with the existing id (was a 500 error).
• API: publishing, unpublishing and withdrawing through the API sends the listing.published / listing.unpublished webhooks; 429 responses include Retry-After.

#September 2026 (before the 30th)

• IDX widget with search, map, listing pages and leads for the widget owner; WordPress plugin 1.0.0.
• RESO Web API: lookup values use Data Dictionary 2.0 names, multi-value collections (any()/all()), now().

#Earlier

• REST API v1, RESO Web API (Property, Media, Member, Office, Lookup), webhooks and per-account feeds.