# Panda IDX - Complete Information Guide > IDX real estate websites, an AI website builder (MAIA) and a real estate CRM for agents, teams and brokerages. ## Company Overview **Name:** Panda IDX, LLC **Location:** 2916 N Miami Ave, Suite 610, Miami, FL 33127, United States **Phone:** +1 (305) 988-2774 **Email:** info@pandaidx.com **Support:** ivan@pandaidx.com **Website:** https://www.pandaidx.com **Documentation:** https://www.pandaidx.com/docs **Business Hours:** Monday-Friday, 9 AM - 6 PM EST **Google rating:** 5.0 (116 reviews) Panda IDX is a real estate technology company in Miami, FL. One platform gives an agent, team or brokerage an IDX website on their own domain, an AI website builder, and a real estate CRM that receives every lead from the website with the listings that lead viewed, saved and searched. The website and the CRM can be bought separately or together. ## Key Facts - Website plans (monthly): Basic $69.99 (1 MLS board, 1 collaborator); Professional $89.99 (up to 2 MLS boards, 2 collaborators, team page); Signature $119.99 (up to 3 MLS boards, unlimited collaborators, CRM included); Custom design + CRM on request. Every website plan has a one-time $500 setup fee. No contracts. - Real Estate CRM sold separately: $49.99/month ($45.99/month billed yearly), no website needed, no setup fee. - Yearly billing: Professional $82.99/month, Signature $110.99/month. - MLS coverage for IDX websites today: Florida, through 5 boards (MIAMI Association of REALTORS, Beaches MLS, Stellar MLS, Naples Area Board of REALTORS, Central Panhandle Association of REALTORS). - Websites can be read in 12 languages: English, Spanish, Portuguese, French, Italian, German, Russian, Chinese, Serbian, Polish, Romanian, Turkish. - AI: MAIA builds and edits the website from a chat; visitors can search listings in plain English; AI assistants can connect through MCP servers. - The CRM does not depend on an MLS feed. - 14 website integrations, plus outbound webhooks that send new leads to Zapier, Make or n8n. - Developers: REST API, React widgets (@pandaidx/widgets) and MCP servers. ## All Website Pages ### Main pages - Home: https://www.pandaidx.com - Pricing: https://www.pandaidx.com/pricing ### Products - IDX Websites: https://www.pandaidx.com/idx-websites-for-realtors - Real Estate CRM: https://www.pandaidx.com/real-estate-crm - AI Website Builder: https://www.pandaidx.com/real-estate-website-builder - AI (MAIA): https://www.pandaidx.com/real-estate-ai - Logo Design: https://www.pandaidx.com/real-estate-logo-design - SEO for Realtors: https://www.pandaidx.com/lp/seo-geo ### Features - All Features: https://www.pandaidx.com/features - Property Search: https://www.pandaidx.com/features/idx-property-search - Condo Directory: https://www.pandaidx.com/features/condo-directory - New Developments: https://www.pandaidx.com/features/new-developments - Home Valuation: https://www.pandaidx.com/features/home-valuation - Lead Capture: https://www.pandaidx.com/features/lead-capture - Lead Tracking & Routing: https://www.pandaidx.com/features/lead-tracking - Deals & Pipelines: https://www.pandaidx.com/features/deals-pipeline - Email Campaigns: https://www.pandaidx.com/features/email-campaigns - Calendar & Tasks: https://www.pandaidx.com/features/calendar-tasks - Analytics: https://www.pandaidx.com/features/analytics - Team Websites: https://www.pandaidx.com/features/team-websites - Multilingual Websites: https://www.pandaidx.com/features/multilingual-websites ### Platform - Integrations: https://www.pandaidx.com/integrations - MLS Coverage: https://www.pandaidx.com/mls-coverage - Developers & API: https://www.pandaidx.com/developers ### Company - Website Examples: https://www.pandaidx.com/real-estate-website-examples - Reviews: https://www.pandaidx.com/reviews - Our Core Values: https://www.pandaidx.com/core-values - About: https://www.pandaidx.com/about - Contact: https://www.pandaidx.com/contact - Case Studies: https://www.pandaidx.com/case-studies ### Resources - FAQ: https://www.pandaidx.com/faq - Panda Academy: https://www.pandaidx.com/tutorials - Blog: https://www.pandaidx.com/blog - News: https://www.pandaidx.com/news ### Demos - Request IDX Demo: https://www.pandaidx.com/request-idx-demo - Request CRM Demo: https://www.pandaidx.com/request-crm-demo ### Legal - Privacy Policy: https://www.pandaidx.com/privacy-policy - Terms & Conditions: https://www.pandaidx.com/terms-and-conditions ### MLS board pages - MIAMI Association of REALTORS: https://www.pandaidx.com/mls/miami-realtors - Beaches MLS: https://www.pandaidx.com/mls/beaches-mls - Stellar MLS: https://www.pandaidx.com/mls/stellar-mls - Naples Area Board of REALTORS: https://www.pandaidx.com/mls/naples-nabor - Central Panhandle Association of REALTORS: https://www.pandaidx.com/mls/central-panhandle ### Comparisons - Panda IDX vs. Luxury Presence: https://www.pandaidx.com/compare/luxury-presence - Panda IDX vs. AgentFire: https://www.pandaidx.com/compare/agentfire - Panda IDX vs. IDX Broker: https://www.pandaidx.com/compare/idx-broker - Panda IDX vs. IDX Boost: https://www.pandaidx.com/compare/idx-boost ### Documentation - Account: https://www.pandaidx.com/docs/account-settings - Analytics: https://www.pandaidx.com/docs/analytics - Get started: https://www.pandaidx.com/docs - Integrations: https://www.pandaidx.com/docs/integrations - Notifications: https://www.pandaidx.com/docs/notifications - Authentication: https://www.pandaidx.com/docs/api-reference/authentication - Get Contacts: https://www.pandaidx.com/docs/api-reference/get-contacts - API Reference: https://www.pandaidx.com/docs/api-reference - MCP Server for AI Integrations: https://www.pandaidx.com/docs/api-reference/mcp-server - Calendar: https://www.pandaidx.com/docs/crm/calendar - Contacts: https://www.pandaidx.com/docs/crm/contacts - Deals: https://www.pandaidx.com/docs/crm/deals - Dashboard: https://www.pandaidx.com/docs/crm - Tasks: https://www.pandaidx.com/docs/crm/tasks - Collections: https://www.pandaidx.com/docs/lead-capture/collections - Forms: https://www.pandaidx.com/docs/lead-capture/lead-forms - Likes: https://www.pandaidx.com/docs/lead-capture/likes-favorites - Searches: https://www.pandaidx.com/docs/lead-capture/saved-searches - Content: https://www.pandaidx.com/docs/website-builder/content - Dashboard, Domains and Contributors: https://www.pandaidx.com/docs/website-builder/dashboard - Website Languages: https://www.pandaidx.com/docs/website-builder/languages - Stories: https://www.pandaidx.com/docs/website-builder/stories - Area Libraries: https://www.pandaidx.com/docs/website-builder/pages/area-libraries - Contact Page: Background Image & Lead Form: https://www.pandaidx.com/docs/website-builder/pages/contact-page - Website General Settings: https://www.pandaidx.com/docs/website-builder/pages/general-settings - Homepage Setup: https://www.pandaidx.com/docs/website-builder/pages/homepage - New Developments: Publish Pre-Construction: https://www.pandaidx.com/docs/website-builder/pages/new-developments - Off-Market Listings: https://www.pandaidx.com/docs/website-builder/pages/offmarket-listings - Profile Page: Bio, Reviews, Videos & Quote: https://www.pandaidx.com/docs/website-builder/pages/profile-page - Team: https://www.pandaidx.com/docs/website-builder/pages/team-page - API Reference: https://www.pandaidx.com/docs/api - Widgets: https://www.pandaidx.com/docs/widgets --- ## Products ### 1. IDX Real Estate Websites Page: https://www.pandaidx.com/idx-websites-for-realtors Websites on the agent's own domain (or a free pandaidx.com subdomain) with live MLS search: map and filters, plain-English AI search, listing pages with a printable MLS sheet, favorites, collections, saved searches with email alerts, a condo directory with a page per building, new developments, area pages, home valuation, off-market listings, team and agent profile pages, Stories (blog), forms and popups, SEO settings and 12 languages. Hosting and SSL are included in every plan. ### 2. Website Editor (Edit Site, Brand Kit, MAIA in early access) Page: https://www.pandaidx.com/real-estate-website-builder · AI overview: https://www.pandaidx.com/real-estate-ai Edit Site shows every page as a visual canvas where the owner adds, reorders and edits sections from a side panel, with undo and redo. Brand Kit applies colors, fonts and spacing to every page, including the property search. Nothing goes live until the owner publishes, and publishing is versioned. MAIA, an AI assistant inside Edit Site, is in early access (turned on per account by the Panda team): it designs sections from a chat, writes and translates content and generates images. MAIA runs on AI credits (Professional 10 a month, Signature 40, extra packs available); editing by hand in Edit Site does not use credits. ### 3. Real Estate CRM Page: https://www.pandaidx.com/real-estate-crm Contacts with the activity from the website (searches, listing views, likes, saved searches, collections, shares), segments, hot-lead alerts, round-robin lead routing with a follow-up plan of tasks, deals and pipelines (buyer, seller, rental, new developments), email campaigns and email templates, tasks, a calendar with one-way Google Calendar sync and a subscribable calendar feed, team roles, CSV import with AI column matching, outbound lead webhooks and a CRM API. Sold on its own for $49.99 a month or included in Signature. ### 4. Lead Capture Page: https://www.pandaidx.com/features/lead-capture Forms built in the dashboard (Contact, Request Showing, Home Valuation and New Development templates, or blank), popups with page targeting, triggers and frequency, and visitor sign-up (email or Google) to save homes and searches. Every submission creates a contact in the CRM and a notification. ### 5. Analytics Page: https://www.pandaidx.com/features/analytics Page views, visitors and conversions per period, conversions by form and popup, UTM sources and campaigns, referrers, countries and browsers. Built into every Panda website with nothing to install. Google Analytics, Google Tag Manager and Facebook Pixel can run alongside it as integrations. ### 6. Team Websites Page: https://www.pandaidx.com/features/team-websites A team page and an individual page per agent with portrait, bio, languages, contact details and their MLS listings. Available from Professional (up to 2 collaborators); Signature has unlimited collaborators. Lead routing shares new website leads in turns among the site owners and admins you choose. ### 7. Multilingual Websites Page: https://www.pandaidx.com/features/multilingual-websites Every Panda website reads in 12 languages (English, Spanish, Portuguese, French, Italian, German, Russian, Chinese, Serbian, Polish, Romanian, Turkish) on the same domain, selected with ?lang= links and remembered for the visit. Menus, labels, section texts and forms are translated; long texts such as MLS descriptions and blog articles stay in their original language unless the owner adds a translation. Pages declare hreflang alternates. ### 8. Logo Design Page: https://www.pandaidx.com/real-estate-logo-design Logo design for agents, teams and brokerages. ## Feature Details All features: https://www.pandaidx.com/features ### Property Search (IDX) Page: https://www.pandaidx.com/features/idx-property-search Map search, filters, plain-English AI search and saved-search alerts. Live MLS listings on your own domain, with a map buyers can draw on, filters for the details that matter in your market, and a search box that understands plain English. **Your MLS, Searchable on Your Website:** Listings from your MLS board sync to your site and show up with photos, details, a map and the disclaimer your board requires. Visitors start from the search box on your homepage, type a city, a building, a zip code, an address or an MLS number, and land on results they can sort by price, newest, beds or baths. Every search has its own clean address, so a link to “homes for sale in Coral Gables” opens exactly that. - **Search the Map, Not Just a City Name:** Buyers rarely think in city limits. They think “east of the highway” or “walking distance to the school.” On the map they can drag to search the area on screen, draw a freehand shape around the blocks they want, or set a radius around a point. Results update to match the boundary, and one click removes it. Listings in the same building are grouped on the map so a tower with forty units does not hide everything around it. - **Filters for the Details That Decide a Sale:** Beyond price, beds and baths, visitors can filter by status (active, under contract, pending, sold or rented), property type, square feet, lot size, year built, HOA fee and garage spaces. Waterfront buyers can pick bay, canal, intracoastal, lake, ocean access or ocean front, and whether there are fixed bridges. Feature filters cover pool, boat dock, gated community, pets allowed, furnished, penthouse, tennis and golf. There is also a filter for how recently a home was listed, from the last 24 hours to the last 90 days. - **Type It the Way You Would Say It:** Some visitors do not want to open six menus. They can write “3 bedroom condo in Brickell under $900K built after 2010” and the AI search turns the sentence into the same filters, runs the search and shows a short description of what it understood. From there they can adjust any filter by hand. It works for beds, baths, price, living area, lot size, year built and location. - **Every Search Tells You Something:** When a visitor likes a home, adds it to a collection or saves a search, they sign up with their email or with Google. From then on their activity is attached to their contact in your CRM: what they searched, which listings they opened and what they saved. A saved search can email them new matches daily or weekly, with your name on the email, so they come back to your site and not to a portal. (Likes, Collections, Saved Searches, Daily or weekly email updates) - **Listing Pages That Ask for the Showing:** Each listing opens with a photo gallery, a map with a Street View link, the full details table, nearby schools and a mortgage calculator with an estimated payment. The Request Showing button opens your own form, and the lead comes to you. Visitors can share the listing by link, email, WhatsApp, Facebook, LinkedIn, Telegram or X, and print a clean MLS Sheet with your logo in the footer. - **Search Pages With Addresses Google Can Read:** For sale, for rent, sold, rented, pending and under contract each have their own address, and so do commercial, land, multi-family and business searches. Combine one with a city or a building and you have a page you can link from your menu, your blog or an ad. ### Condo Directory (IDX) Page: https://www.pandaidx.com/features/condo-directory Every building as its own page, with live listings, amenities and sales stats. Condo buyers shop by building. Give them a directory where each tower has its photos, amenities, sales stats and the units available right now. **Browse by Area, Then by Building:** The directory opens with your areas in rows, each with its buildings as cards that show a live price range and how many units are for sale and for rent. A visitor can pick an area, search a building by name, switch between sale and rental inventory, sort the results and open the map to see where each building sits. - **A Page for Every Building:** Each building page has a photo gallery, a description, the facts buyers ask about (year built, stories, total units), the amenities, and sales statistics. Below that are the listings inside the building, split into for sale, for rent and sold, as regular listing cards a visitor can like, add to a collection or open. A map shows the location, and a lead form sits on the page so the question “is this unit still available?” reaches you. - **Filters Made for Condos:** A single-family search asks about lot size. A condo search asks about the building. The directory filters by price range, beds and baths, property type, views and waterfront, year built, number of stories and total units. Someone who wants a boutique building from the last ten years with a bay view can get to a short list in three clicks. - **Area Pages That Explain the Neighborhood:** Every area has its own page with a description, market counters, price statistics, walk, transit and bike scores, an outline of the area on the map and all of its buildings. It is the page you send to a client who is relocating and asks “what is Edgewater like?” and it is a page that can rank for that neighborhood’s condo searches. - **Put Your Buildings on Your Homepage:** Group buildings into libraries and place them on your homepage or any page: the towers you specialize in, a waterfront collection, new buildings in one neighborhood. The directory comes with seven display templates, including grid, carousel, featured and showcase layouts, so the section matches the rest of your site. - **Building Interest Shows Up in Your CRM:** When a signed-in visitor opens a building or an area, searches the directory or likes a unit, it is recorded on their contact. You can see that a buyer keeps returning to the same two buildings before you call them. ### New Developments (IDX) Page: https://www.pandaidx.com/features/new-developments Pre-construction projects with floor plans, deposit schedules and a lead form that goes to you. A directory of new developments with the details buyers and investors ask for first: prices, floor plans, deposit schedule and delivery. Every inquiry goes to you. **A Directory of What Is Being Built:** Pre-construction rarely lives in the MLS, so most agent websites have nothing to show for it. The New Developments directory fills that gap. Visitors filter by country, city, status, price and project name, browse projects in rows by area, and see each one as a card with the developer, the number of units and the asking range. A map shows where each project stands. - **The Project Page Buyers Expect:** Each development has a page with a photo gallery, a description, the brochure and a video when available, and the specifications: asking prices, unit sizes, number of units, developer and architect. Amenities are listed in full. Floor plans are on the page, and so is the deposit schedule, which is usually the first thing an investor asks about. - **Inquiries Go to You, Not the Sales Center:** The lead form on a project page belongs to your website. When someone asks for pricing or a presentation, the inquiry goes to you and is saved as a contact in your CRM, never to the developer’s sales team. You decide how to follow up and which projects to recommend. You can also edit that form, so it asks what you need to know: budget, timeline, whether they are buying to live or to invest. - **Resales Next to New Inventory:** When a building is delivered and units start to trade, the resale listings from your MLS appear on the same project page. A buyer comparing developer inventory with a resale on the 30th floor sees both without leaving your site, and the page stays useful after the sales center closes. - **Feature the Projects You Sell:** Pick the developments you represent and feature them on your homepage, with a photo slider, price range and a link to the full directory. In the CRM, the New Developments pipeline template tracks these buyers through the stages that apply to pre-construction: Presentation / Tour, Reservation / Deposit and Contract Signed. ### Home Valuation (IDX) Page: https://www.pandaidx.com/features/home-valuation An instant estimate from comparable sales that brings sellers into your CRM. A homeowner types an address and gets an estimate based on comparable sales from your MLS. You get a seller lead with the address attached. **“How Much Is My Home Worth?” Answered on Your Site:** Homeowners ask that question long before they call an agent, and they usually ask a portal. With Panda the page lives on your website. The owner starts typing an address, picks it from the suggestions and sees the Panda Estimate: a value with a low and high range and a confidence level, calculated from comparable sales in your own MLS feed. - **An Estimate People Can Check:** A number with no explanation does not earn trust. The report shows the comparable sales behind the estimate and places them on a map around the home, so the owner can see which houses were used. It adds the home’s own sale history and a market snapshot for the area, with the price per square foot trend and how prices are distributed. The owner can share the report with a spouse or a partner from the same page. - **Every Estimate Is a Seller Lead:** The valuation page uses a form you control. Decide what to ask (name, email, phone, when they plan to sell) and what happens after they submit. The submission creates a contact in your CRM like any other website lead, and you are notified right away. Now you know who is thinking about selling, where the home is and what the estimate said, which is everything you need to offer a proper pricing conversation. - **Market Numbers for Your Areas:** Sellers also want context. Market Pulse shows several areas side by side with figures from your MLS, refreshed every hour: homes for sale and the change from last week, months of supply, whether it is a seller’s or a buyer’s market, and the medians from the last three months of closings for sale price, price per square foot, days on market and sale-to-list ratio. - **An Estimate, Not an Appraisal:** The Panda Estimate is a starting point based on recent sales. It does not see a renovated kitchen, a view or deferred maintenance. That gap is your opening: the page gives the owner a number, and you offer the walkthrough that makes it accurate. ### Lead Capture (Websites) Page: https://www.pandaidx.com/features/lead-capture Forms, popups and visitor sign-up that send every lead to your CRM. Forms you design, popups that appear at the right moment, and a sign-up that turns anonymous visitors into contacts with a search history. **Three Ways a Visitor Becomes a Lead:** A visitor fills in a form: contact, showing request, home valuation or a project inquiry. A visitor answers a popup. Or a visitor signs up to save a home or a search. All three create the same thing: a contact in your CRM with a source, plus a notification to you. You manage all of it from your dashboard, without code and without a third-party form tool. - **Forms You Build Yourself:** Start from a template (Contact, Request Showing, Home Valuation, New Development) or from a blank form. Add text, email, phone, dropdown, checkbox, date, time and long-text fields, mark the required ones and put them in the order you want. Then assign the form to a spot on your website: the contact page, the valuation page, the showing request on listings, project pages, the newsletter sign-up or the careers page. After someone submits, show a thank-you message, send them to another page or give them a document to download. - **Popups With Rules:** A popup can hold any of your forms, the sign-up form or the login screen. You choose the pages where it appears: the homepage, every page, listing pages only or exact addresses. You choose the trigger: after a delay of up to 60 seconds, at a scroll depth, on exit intent, or after a visitor has opened a set number of listings. And you choose the frequency: always, once per session or once ever. Popups can be made non-dismissable when you want sign-up before someone keeps browsing listings. - **Sign-Up That Feels Like a Feature:** Visitors create an account to keep what they find: liked homes, collections and saved searches with email updates. They sign up with email and password or continue with Google, and give their phone number with consent. For you, that account is a contact whose activity you can follow in the CRM, which is worth more than a name and an email from a generic “contact us” box. - **Where the Lead Goes Next:** Each submission lands in your CRM as a contact and triggers a notification. With lead routing on, new leads are shared in turns among the owners and admins you choose, and a follow-up plan can create the first tasks automatically. If you use another system, an outbound webhook (https://www.pandaidx.com/integrations) sends every new lead to it. You can add up to five endpoints, each request is signed, and it works with Zapier, Make and n8n. - **Know Which Popup Works:** Analytics counts conversions per popup and per form, next to page views and visitors, and breaks them down by source and UTM campaign. You can see that the valuation popup on your blog converts and the one on your homepage does not, and change it the same day. ### Team Websites (Websites) Page: https://www.pandaidx.com/features/team-websites A team page, a profile for every agent and each agent’s own listings. One brand, one IDX search, and a profile for each person on the team with their bio, their contact details and their own listings. **Meet the Team, on One Page:** The team page presents your people as portrait cards with name, title, email and phone. Management appears first, followed by your associates, and each card links to that person’s own page. A “Join the Team” button sits at the top for recruiting and opens a careers form you design. Add someone in your dashboard and the page updates. - **A Real Profile for Each Agent:** Every member page has the agent’s portrait or an intro video, title, email, phone, the languages they speak, social links and a full bio. Below it are their MLS listings, split into active and sold, pulled from the feed by their agent ID, so there is nothing to upload by hand. The team leader’s profile can also show the office’s listings and a video gallery. It is the page an agent puts in their email signature. - **Roles That Match the Job:** Not everyone needs the keys to everything. Invite each collaborator with a role: Owner, Admin, Agent, Website Editor, Blogger, Billing or Vendor. Your marketing coordinator can edit pages and publish stories without seeing billing. A writer can post to the blog and nothing else. Each person fills in their own profile, with photos, biography, social links, phone numbers and languages. - **Leads Shared Fairly:** With the CRM, new website leads can be shared in turns among the owners and admins you choose (the members who can own leads), so no one has to decide by hand who gets the next inquiry. Each lead has one owner, and the contact list filters by owner. A follow-up plan gives that owner the first tasks, and the team works from the same pipelines and the same calendar. - **One Brand, Many Voices:** Client reviews have their own page and can appear in a section on your homepage. Stories, the blog of your website, shows each article with its author. The Brand Kit keeps colors, typography and components consistent across every page, however many people publish. - **How Many People Can Collaborate:** Basic includes one collaborator, Professional includes two and the team page, and Signature includes unlimited collaborators plus the CRM. A custom plan is available for brokerages that need their own design. ### Multilingual Websites (Websites) Page: https://www.pandaidx.com/features/multilingual-websites Twelve languages on every page, with no extra setup. Your international buyers can search listings, read your pages and fill in your forms in their own language. All twelve languages are on from the first day. **Twelve Languages, Always On:** Every page of a Panda website is available in English, Spanish, Portuguese, French, Italian, German, Russian, Chinese, Serbian, Polish, Romanian and Turkish. There is nothing to install and no language to buy or switch on. A visitor chooses a language from the chooser in your header, and the site remembers it, so every page they open afterward is in that language. - **The Search, Translated:** The parts of your site a buyer uses most are the ones that change language: menus, buttons, filters, listing types and statuses, amenities and features, your section texts and your lead forms. A buyer from São Paulo can filter for an oceanfront condo and send a showing request in Portuguese. Short texts are translated by AI the first time a language is requested and then saved, so the next visit loads without waiting. - **Your Wording Wins:** Machine translation is a starting point, and some phrases deserve your own voice: your headline, your tagline, the way you describe your service. In Edit Site, ask MAIA (https://www.pandaidx.com/real-estate-ai) to show a language, type your version directly on the page, and it is saved as your translation for that language. From then on the website shows yours. Texts that must never change, such as a brand name, can be marked to stay as written in every language. - **One Address per Page, Every Language:** The language is never part of the page address. Your team page is /team in every language, and a link ending in ?lang=es opens it in Spanish. That keeps your links simple: the same URL works in an ad, an email or a QR code, and you add the language only when you want to force one. Search engines find each language through hreflang tags on every page, with English as the default. - **What Stays as Written:** Long texts are not machine-translated. The MLS description of a listing, a blog article or a long bio appear in the language they were written in, unless you add your own translation. That is deliberate: a listing description is the listing agent’s text, and a mistranslated legal or property detail causes more trouble than an English paragraph. - **A Language Chooser That Fits Your Header:** The chooser is not a fixed widget. Describe the one you want to MAIA, for example a round flag next to your social icons with a dropdown of all languages, and MAIA designs it to match your site. It shows the current language and reloads the same page in the one a visitor picks. ### Analytics (Websites) Page: https://www.pandaidx.com/features/analytics Page views, visitors, conversions and where they came from. How many people visited, which pages they read, where they came from and which ones became leads. One page in your dashboard, already set up. **Three Numbers First:** The Analytics page opens with Page Views, Visitors and Conversions for the period you choose: the last 24 hours, 7 days, 30 days, 3 months or 12 months. Switch the chart between the three metrics to see the trend. There is nothing to install and no tag to paste. Your Panda website reports to it from the day it goes live. - **See What Becomes a Lead:** Traffic is only interesting if it turns into contacts. Conversions lists the forms and popups that produced leads in the period, so you can tell whether the contact page, the showing request or the valuation form is doing the work. Popups have their own table with trigger, delay, frequency and results side by side. If a popup gets views and no sign-ups, change the timing and compare next week. - **Know Which Marketing Pays:** Add UTM parameters to the links in your ads, emails and social posts, and Analytics breaks visits and conversions down by Source, Medium, Campaign, Term and Content. The Referers list shows the sites that send you people. When you are paying for a campaign, you can see how many visitors it sent and how many of them filled in a form. - **Understand Who Is Visiting:** Pages shows which parts of your site get read: listings, building pages, your blog, your profile. Countries tells you whether that international audience you advertise to is arriving. Browsers, operating systems and devices show how people reach you, which usually means a phone. Filter the whole dashboard by a page, an event or a single visitor to follow one path from first click to conversion. - **Built for a Listing Website:** Generic analytics tools count pages. This one also knows what a listing is. It records listing views, likes, saved searches, additions to collections and shares, next to page views and form submissions. The same events appear on each signed-in visitor’s contact in the CRM, so the totals in Analytics and the timeline of a lead describe the same visits. (Page views, Listing views, Likes, Saved searches, Collection adds, Shares, Form and popup conversions) ### Lead Tracking & Routing (CRM) Page: https://www.pandaidx.com/features/lead-tracking See what each lead searched and saved, get hot-lead alerts and share new leads in turns. Know what each lead is looking at on your website, hear about it when they get serious, and make sure someone on your team owns the follow-up. **The Website Fills In the Contact for You:** A lead who registered on a portal is a name and a phone number. A lead who registered on your Panda website arrives with context: the searches they ran, the listings they opened, the homes they liked, the collections they built and the searches they saved. It is all on the contact, in order, so your first call can start with “I saw you have been looking at three-bedrooms in Coconut Grove.” - **One Timeline per Person:** Open a contact and you get tabs for Overview, Activity, Saved and Collections, next to their notes, tasks, deals and documents. Activity lists website behavior: property searches, listings and buildings opened, areas viewed, likes, shares and saved searches. It also holds what you did: notes, logged calls, emails and appointments. You can log a call with its date, direction and result, write a note, create a task or book an appointment without leaving the contact. - **Alerts When a Lead Heats Up:** Panda marks a contact as a hot lead when their behavior changes: they open the same listing three times in one visit, look at five or more listings in one visit, come back after two weeks or more away, or save a home or a search after browsing several listings. You get an email that says who it is and why, with a link to the contact. There is at most one alert per contact per day, so a busy visitor does not flood your inbox. - **New Leads Shared in Turns:** On a team, the worst outcome is a lead nobody claims. Turn on “Share new leads in turns” and each new website lead is assigned to the next person in line, among the members you select (site owners and admins can own leads). In the contact list you can filter by owner, see your own leads or find the ones with no owner. Leads are spread evenly, and everyone knows which ones are theirs. - **A Follow-Up Plan for Every New Lead:** Speed matters most in the first week. The Follow-up Plan creates tasks for the lead’s owner as soon as a website lead arrives. The default plan is a call the same day, a reminder to text a few homes the next day, a market update email on day three and a check-in on day seven. Edit the steps, add up to ten and schedule them as far as ninety days out. The tasks show up in Tasks and on the calendar with the lead’s name already in the title. - **Keep the List Clean:** Group contacts into segments such as buyers, sellers, investors or past clients, and use those segments as campaign audiences (https://www.pandaidx.com/features/email-campaigns). Import a spreadsheet and let AI match its columns to contact fields. Merge duplicates, and export whenever you need the data elsewhere. ### Deals & Pipelines (CRM) Page: https://www.pandaidx.com/features/deals-pipeline Boards for buyers, sellers, rentals and new developments, with value and commission on each deal. One board per type of business, with the stages you actually use and the numbers that tell you what the month looks like. **See Where Every Deal Stands:** The Deals page shows each pipeline as a board. Every column is a stage, every card is a deal, and each card shows the people involved. Move a deal to the next column when it advances. Switch pipelines from the tabs at the top, which also show how many deals each one holds. Monday morning’s question, “what is open and what is stuck,” has an answer on one screen. - **Templates for How Real Estate Works:** A buyer does not move through the same steps as a listing. Start a pipeline from a template and the stages are already there. Buyer goes from New Lead and Contacted to Qualified Buyer, Showing Scheduled, Offer Made, Under Contract and Closed. Seller covers Listing Appointment, Listing Agreement Signed, Active Listing and Offer Received. Rental tracks Property Showing, Application Submitted and Lease Signed. New Developments adds Presentation / Tour and Reservation / Deposit. Or start from Blank and name the stages yourself. - **The Numbers on Every Deal:** Each deal carries a Deal Value, a Projected Close Date, the Property Address and the Commission Total. That is enough to know what is likely to close this quarter and what it is worth to you. The CRM dashboard adds it up, with deal statistics and earned commission next to your contact numbers, so you can check your pipeline without opening a spreadsheet. - **People, Not Just Addresses:** A deal usually involves more than one person: both spouses, a co-buyer, the tenant and the owner. Add several contacts to the same deal and open any of them from the card. From a contact you can see their linked deals, and from a deal you can reach each person’s timeline, including what they searched and saved on your website. - **Your Stages, Your Colors, Your Order:** Rename a stage, add one, give each a color and reorder the pipeline tabs. Run as many pipelines as you have lines of business: buyers, listings, rentals, pre-construction, property management. A team shares the same boards, so nobody has to ask for a status update. ### Email Campaigns (CRM) Page: https://www.pandaidx.com/features/email-campaigns Design an email, pick a segment, schedule it and read the report. Design the email, pick who gets it, choose when it goes out and read the report. Your contacts and your campaigns are in the same place, so there is nothing to export. **From Blank Page to Sent in One Sitting:** Create a campaign, give it a name and choose a design: one of the templates, one of your saved designs or a blank canvas. Write the subject and the preview text, set the From name and the reply-to address, pick the audience and decide whether it goes now or later. Before it reaches anyone, send yourself a test and check it on desktop and mobile. - **An Editor Made for Email:** Build the message from blocks: headings, text, images, buttons, dividers, columns, icon-and-text rows and social links. Start from a design such as “Just listed” or “An open invitation,” or from a plain layout when a short personal note works better. Set fonts, colors and spacing once in Styles and every block follows, and adjust text size and padding separately for mobile. Save a design to reuse it in the next campaign. Images come from your Media Center. - **Send to the Right Segment:** A new-listing email should not go to a client who closed last month. Choose All contacts or specific segments as the audience, and use “Don’t send to” to leave a segment out. Before sending you can open the audience and see exactly which contacts are in it. Contacts who unsubscribed or whose address bounced are suppressed for you. - **Schedule Once or Repeat Weekly:** Send now, or schedule the first send for a date and time. A campaign can also repeat weekly on the weekdays you choose and stop after a date you set, which suits a Friday open-house roundup or a Monday market note. Scheduled campaigns appear on your CRM calendar. You can pause sending, reschedule or stop delivery at any point. - **A Report You Can Act On:** Each campaign reports sent, delivered, opened, clicked, bounced, unsubscribed and complained, with open, click, bounce and unsubscribe rates. Opens and clicks made by mail-scanning software are counted separately as automatic activity, so the rates reflect people. See the top links clicked, filter recipients by what they did, and open any contact from the list to follow up with the ones who clicked on the listing. ### Calendar & Tasks (CRM) Page: https://www.pandaidx.com/features/calendar-tasks Tasks with time slots and a month calendar that syncs to Google Calendar. Calls, showings, open houses and closings in one month view, tied to the contacts they are about and synced to the calendar on your phone. **The Month at a Glance:** The calendar fills the screen and shows the whole month without scrolling. Events that span several days appear as bars in the color you pick. Tasks sit on their due date with a checkbox, and client birthdays show up on their day. Click anything for its details, or double-click a day to create an event on the spot. - **Tasks Built Around Clients:** Every task has a category with its own color and icon: Call, Email, Text, Follow Up, Showing, Open House, Closing and Thank You. Give a task a date and a time slot, and assign it to a contact so the person’s name and history are one click away. The Tasks page filters by pending, completed and overdue, and has a search box for when you remember the client but not the day. Checking a task off updates the list right away. - **Synced to Google Calendar:** Connect Google Calendar (https://www.pandaidx.com/integrations) and your Panda events and dated tasks appear there, updated in near real time. It is a one-way sync from Panda to Google, so your Panda calendar stays the source for client work while your phone shows the full day. If you use another calendar app, Share Calendar gives you a private calendar URL to subscribe to, with a “busy only” option when you want to share availability without the details. - **Follow-Up That Creates Itself:** Not every task starts with you. When a new lead arrives from your website, the Follow-up Plan adds the first tasks for the lead’s owner: a call today, a reminder to text tomorrow, an email on day three, a check-in after a week. They land in Tasks and on the calendar with the lead’s name in the title. Panda also sends reminders for tasks that are due, so the plan does not depend on you remembering to look. - **One Place for the Day’s Work:** The CRM dashboard shows your upcoming tasks and calendar events next to your contact and deal numbers. From a contact you can create a task or book an appointment without leaving the page, and it appears on the calendar. Scheduled email campaigns show up there too, so you can see what your contacts will receive this week. --- ## MLS Coverage Coverage page: https://www.pandaidx.com/mls-coverage IDX websites connect to these Florida MLS boards today. The agent needs an active membership with each board connected to the site. Basic includes one board, Professional up to two and Signature up to three. - **MIAMI Association of REALTORS** (MIAMI REALTORS): Miami-Dade, Broward and Palm Beach. Counties: Miami-Dade, Broward, Palm Beach. https://www.pandaidx.com/mls/miami-realtors - **Beaches MLS** (Beaches MLS): Palm Beach, Broward and the Treasure Coast. Counties: Palm Beach, Broward, St. Lucie, Miami-Dade, Martin, Indian River, Okeechobee. https://www.pandaidx.com/mls/beaches-mls - **Stellar MLS** (Stellar MLS): Tampa Bay, Orlando, Sarasota and Central Florida. Counties: Pinellas, Hillsborough, Orange, Polk, Charlotte, Sarasota, Marion, Osceola, Pasco, Manatee, Volusia, Lake, Seminole, Hernando, Citrus, Flagler, Alachua, Lee, Highlands, Sumter, Brevard, Putnam, Levy. https://www.pandaidx.com/mls/stellar-mls - **Naples Area Board of REALTORS** (NABOR): Naples, Fort Myers and Southwest Florida. Counties: Lee, Collier, Charlotte. https://www.pandaidx.com/mls/naples-nabor - **Central Panhandle Association of REALTORS** (CPAR): Panama City and the Florida Panhandle. Counties: Bay, Washington, Jackson, Gulf, Walton, Holmes. https://www.pandaidx.com/mls/central-panhandle --- ## Integrations Integrations page: https://www.pandaidx.com/integrations The 14 website integrations are turned on from the dashboard: ### Messaging - **WhatsApp:** A WhatsApp button on your site so visitors can message you from any page. - **Telegram:** A Telegram contact button for clients who prefer it. - **Zoho SalesIQ:** Live chat with visitors through Zoho SalesIQ. ### Analytics - **Meta Pixel:** Measure your Meta ads and retarget the people who visited your listings. - **Google Analytics:** Send your site traffic to your own Google Analytics property. - **Google Tag Manager:** Load your tags and conversion scripts without touching code. - **Zoho PageSense:** Heatmaps and conversion analysis with Zoho PageSense. ### Sign-in - **Google One Tap:** Visitors sign up with their Google account in one tap, so more of them become contacts. ### CRM - **HubSpot:** Add your HubSpot tracking code with your Portal ID to see website visits in HubSpot. - **Follow Up Boss:** Add the Follow Up Boss pixel to track website visits. Send leads to it with a webhook. - **GoHighLevel:** Add your GoHighLevel tracking script and ID. Send leads to it with a webhook. - **Clientify:** Add the Clientify tracking pixel to your website. ### Accessibility - **UserWay:** The UserWay accessibility widget on every page of your site. ### Video - **Webreels:** Show your Webreels property videos on your website. ### Webhooks and API - **Outbound webhooks:** every new lead is posted to up to five endpoints, each request signed so the receiver can verify it. Works with Zapier, Make and n8n. - **CRM API:** create and update contacts from your own systems with a secret API key (see API & Developer Tools below). - **Google Calendar:** one-way sync of calendar events and tasks with a due date from Panda to Google Calendar. Apple Calendar, Outlook and other apps can subscribe to a read-only calendar URL. --- ## Pricing - **Basic** (IDX Website): $69.99/month, $64.99/month billed yearly, one-time $500 setup fee. A professional IDX website for one agent and one MLS. Includes: Real estate IDX website; 1 MLS board; 1 collaborator; Condo directory and new developments; Free subdomain or your own domain. - **Professional** (IDX Website): $89.99/month, $82.99/month billed yearly, one-time $500 setup fee. For agents who sell across two MLS boards or work with an assistant. Includes: Everything in Basic; Up to 2 MLS boards; Up to 2 collaborators; Team page; Website analytics. - **Signature** (IDX Website + CRM): $119.99/month, $110.99/month billed yearly, one-time $500 setup fee. Your website and the Panda CRM together, for agents and teams. Includes: Everything in Professional; Up to 3 MLS boards; Unlimited collaborators; Real Estate CRM included. - **Custom** (Custom Design + CRM): price on request. A custom-designed website and the CRM for brokerages and large teams. Includes: Custom website design; Real Estate CRM; Unlimited collaborators; Onboarding for your whole team. - **Real Estate CRM** (No website needed): $49.99/month, $45.99/month billed yearly, no setup fee. Contacts, deals, email campaigns, tasks and calendar for agents who already have a website. Includes: Contacts and segments; Deals and pipelines; Email campaigns and templates; Tasks and calendar; Up to 2 collaborators. Every website plan (Basic, Professional and Signature) carries a one-time $500 setup fee; the CRM sold on its own does not. Basic and Professional can add the CRM for $49.99 a month. There are no contracts: plans renew month to month (or yearly at a lower monthly rate) and can be changed or canceled from the billing portal. Hosting and SSL are included in every website plan. MAIA runs on AI credits; Professional and Signature include credits every month and extra packs are available. Current prices: https://www.pandaidx.com/pricing ### How Panda IDX compares Competitor pricing as published on their own sites (checked November 2026): - **Luxury Presence:** setup $2,500–$3,500 setup, depending on plan; monthly From $295; 12-month agreement. Comparison: https://www.pandaidx.com/compare/luxury-presence - **AgentFire:** setup $800 · $2,750 custom · $6,500 Firebrand; monthly From $165; Month-to-month. Comparison: https://www.pandaidx.com/compare/agentfire - **IDX Broker:** setup $100 one-time (developer partner pricing page); monthly Core from $60 · Engage from $99 · Elite from $145–$149; Month-to-month. Comparison: https://www.pandaidx.com/compare/idx-broker - **IDX Boost:** setup Not published; monthly From $79 (no IDX) · $125 with IDX Lite · $199 IDX Pro; Not published. Comparison: https://www.pandaidx.com/compare/idx-boost - **Custom agencies:** setup Often $5,000–$10,000+; monthly Varies; Varies. - **Panda IDX:** one-time $500 setup; from $69.99 a month; month-to-month, no contract. --- ## Not Available Today Panda does not offer built-in SMS or texting, WhatsApp messaging inside the CRM, drip or workflow automations that message leads step by step, voice agents, a transaction management or e-signature module, or a native mobile app. The CRM's Text button opens the phone's own messaging app; the Follow-up Plan creates tasks, it does not send messages. WhatsApp and Telegram are contact buttons on the website. --- ## API & Developer Tools **Developer hub:** https://www.pandaidx.com/developers **Site API base URL:** https://api.pandaidx.com/v1 **API documentation and tester:** https://www.pandaidx.com/docs/api **OpenAPI 3.1:** https://www.pandaidx.com/openapi.json **Authentication:** - CRM Contacts API (/v1/crm/contacts): a secret API key as `Authorization: Bearer sk_live_…`, created in the dashboard under CRM > Contacts > API Keys. Servers only. Scopes contacts:read and contacts:write, 120 requests per minute per key, Idempotency-Key header on POST. OpenAPI: https://api.pandaidx.com/v1/crm/openapi.json - Site API: the website's public key in the `key` query parameter (pk__). The key selects the account; no OAuth and no secret. Browser calls are allowed from the account's own domains. - Visitor endpoints (favorites, saved searches, profile) also take the signed-in visitor's token: `Authorization: Bearer ` - MCP servers: OAuth 2.1 with PKCE S256 and Dynamic Client Registration at https://app.pandaidx.com. Scopes: profile, listings, contacts, analytics, calendar, collections, saved_searches, email, builder. These tokens work with the MCP servers only. **MCP servers:** - Product MCP (listings, contacts, analytics, calendar, collections, saved searches, email): https://api.pandaidx.com/mcp - Public docs MCP: https://www.pandaidx.com/mcp **Site API endpoints:** ### Authentication - **GET /authorize** — Authorize User: https://www.pandaidx.com/docs/api/authorize - **POST /api/oauth/token** — Exchange Code for Tokens: https://www.pandaidx.com/docs/api/token-exchange - **POST /api/oauth/revoke** — Revoke Token: https://www.pandaidx.com/docs/api/revoke-token - **POST /register** — Register OAuth Client: https://www.pandaidx.com/docs/api/register-client - **GET /.well-known/oauth-authorization-server** — Authorization Server Metadata: https://www.pandaidx.com/docs/api/oauth-metadata ### CRM Contacts - **GET /v1/me** — Check API Key: https://www.pandaidx.com/docs/api/check-api-key - **POST /v1/crm/contacts** — Create or Update Contact: https://www.pandaidx.com/docs/api/upsert-contact - **GET /v1/crm/contacts** — Find Contacts: https://www.pandaidx.com/docs/api/list-contacts - **GET /v1/crm/contacts/:id** — Get Contact: https://www.pandaidx.com/docs/api/get-contact - **PATCH /v1/crm/contacts/:id** — Edit Contact: https://www.pandaidx.com/docs/api/update-contact - **POST /v1/crm/contacts/:id/tags** — Add Tags to Contact: https://www.pandaidx.com/docs/api/add-contact-tags - **DELETE /v1/crm/contacts/:id/tags/:tag** — Remove Tag from Contact: https://www.pandaidx.com/docs/api/remove-contact-tag ### Listings & Saved Searches - **GET /v1/listings** — Search Listings with an API Key: https://www.pandaidx.com/docs/api/find-listings - **POST /v1/crm/contacts/:id/saved-searches** — Save a Search for a Contact: https://www.pandaidx.com/docs/api/create-contact-saved-search - **GET /v1/crm/contacts/:id/saved-searches** — List Saved Searches of a Contact: https://www.pandaidx.com/docs/api/list-contact-saved-searches - **DELETE /v1/crm/contacts/:id/saved-searches/:searchId** — Delete a Saved Search of a Contact: https://www.pandaidx.com/docs/api/delete-contact-saved-search ### Site & Content - **GET /v1/site/status** — Site Status: https://www.pandaidx.com/docs/api/site-status - **GET /v1/site** — Get Site: https://www.pandaidx.com/docs/api/get-site - **GET /v1/team** — List Team: https://www.pandaidx.com/docs/api/list-team - **GET /v1/team/:slug** — Get Team Member: https://www.pandaidx.com/docs/api/get-team-member - **GET /v1/testimonials** — List Testimonials: https://www.pandaidx.com/docs/api/list-testimonials - **GET /v1/videos** — List Videos: https://www.pandaidx.com/docs/api/list-videos - **GET /v1/popups** — List Popups: https://www.pandaidx.com/docs/api/list-popups - **GET /v1/blog** — List Blog Posts: https://www.pandaidx.com/docs/api/list-blog-posts - **GET /v1/blog/categories** — List Blog Categories: https://www.pandaidx.com/docs/api/list-blog-categories - **GET /v1/blog/:slug** — Get Blog Post: https://www.pandaidx.com/docs/api/get-blog-post - **GET /v1/offmarket** — List Off-Market Listings: https://www.pandaidx.com/docs/api/list-offmarket - **GET /v1/offmarket/:slug** — Get Off-Market Listing: https://www.pandaidx.com/docs/api/get-offmarket-listing - **GET /v1/site-blocks** — List Site Blocks: https://www.pandaidx.com/docs/api/list-site-blocks - **GET /v1/site-content** — List Site Content: https://www.pandaidx.com/docs/api/list-site-content - **GET /v1/site-sections** — List Site Sections: https://www.pandaidx.com/docs/api/list-site-sections ### Listings & Search - **GET /v1/search** — Search Listings: https://www.pandaidx.com/docs/api/search-listings - **POST /v1/search** — Search Listings (POST): https://www.pandaidx.com/docs/api/search-listings-post - **GET /v1/search/bootstrap** — Search Bootstrap: https://www.pandaidx.com/docs/api/search-bootstrap - **GET /v1/listings/:listingId** — Get Listing Detail: https://www.pandaidx.com/docs/api/get-listing-detail - **GET /v1/listings/:listingId/private** — Get Listing Private Fields: https://www.pandaidx.com/docs/api/get-listing-private - **GET /v1/featured-listings** — List Featured Listings: https://www.pandaidx.com/docs/api/list-featured-listings - **GET /v1/agent-listings** — List Agent Listings: https://www.pandaidx.com/docs/api/list-agent-listings - **GET /v1/team/:slug/listings** — List Team Member Listings: https://www.pandaidx.com/docs/api/list-team-member-listings - **GET /v1/collections/:slug** — Get Collection: https://www.pandaidx.com/docs/api/get-collection - **GET /v1/saved-searches/:slug** — Get Saved Search: https://www.pandaidx.com/docs/api/get-saved-search - **GET /v1/autocomplete** — Autocomplete: https://www.pandaidx.com/docs/api/autocomplete - **GET /v1/autocomplete-catalog** — Autocomplete Catalog: https://www.pandaidx.com/docs/api/autocomplete-catalog - **GET /v1/autocomplete-catalog/revision** — Autocomplete Catalog Revision: https://www.pandaidx.com/docs/api/autocomplete-catalog-revision - **GET /v1/suggestions** — Search Suggestions: https://www.pandaidx.com/docs/api/search-suggestions - **POST /v1/ai/search** — AI Search: https://www.pandaidx.com/docs/api/ai-search - **GET /v1/schools** — List Schools: https://www.pandaidx.com/docs/api/list-schools - **GET /v1/nearby-places** — List Nearby Places: https://www.pandaidx.com/docs/api/list-nearby-places - **GET /v1/places/autocomplete** — Places Autocomplete: https://www.pandaidx.com/docs/api/places-autocomplete - **GET /v1/home-valuation** — Home Valuation: https://www.pandaidx.com/docs/api/home-valuation - **POST /v1/home-valuation/track** — Track Home Valuation: https://www.pandaidx.com/docs/api/home-valuation-track ### Areas & Buildings - **GET /v1/areas** — List Areas: https://www.pandaidx.com/docs/api/list-areas - **GET /v1/areas/:slug** — Get Area Library: https://www.pandaidx.com/docs/api/get-area-library - **GET /v1/condos** — List Condos: https://www.pandaidx.com/docs/api/list-condos - **GET /v1/condos/areas/:slug** — Get Condo Area: https://www.pandaidx.com/docs/api/get-condo-area - **GET /v1/condos/areas/:slug/market** — Get Condo Area Market: https://www.pandaidx.com/docs/api/get-condo-area-market - **GET /v1/market/:slug** — Get Area Market: https://www.pandaidx.com/docs/api/get-area-market - **GET /v1/market** — List Area Markets: https://www.pandaidx.com/docs/api/list-market-areas - **GET /v1/condos/directory** — Condo Directory Bootstrap: https://www.pandaidx.com/docs/api/condo-directory - **GET /v1/condos/directory/buildings** — Condo Directory Search: https://www.pandaidx.com/docs/api/condo-directory-buildings - **GET /v1/condos/directory/areas** — Condo Directory Landing Rows: https://www.pandaidx.com/docs/api/condo-directory-areas - **GET /v1/condos/directory/area/:slug** — Condo Directory Area: https://www.pandaidx.com/docs/api/condo-directory-area - **GET /v1/buildings/:slug** — Get Building: https://www.pandaidx.com/docs/api/get-building - **GET /v1/buildings/:slug/listings** — List Building Listings: https://www.pandaidx.com/docs/api/list-building-listings - **GET /v1/new-developments** — List New Developments: https://www.pandaidx.com/docs/api/list-new-developments - **GET /v1/new-developments/directory** — New Developments Directory: https://www.pandaidx.com/docs/api/new-developments-directory - **GET /v1/new-developments/:slug** — Get New Development: https://www.pandaidx.com/docs/api/get-new-development - **GET /v1/new-developments/:slug/listings** — List New Development Listings: https://www.pandaidx.com/docs/api/list-new-development-listings ### Libraries & Forms - **GET /v1/libraries** — List Libraries: https://www.pandaidx.com/docs/api/list-libraries - **GET /v1/libraries/:id** — Get Library: https://www.pandaidx.com/docs/api/get-library - **GET /v1/forms/:spot** — Get Form By Spot: https://www.pandaidx.com/docs/api/get-form-by-spot - **GET /v1/forms/by-id/:id** — Get Form By ID: https://www.pandaidx.com/docs/api/get-form-by-id - **POST /v1/forms/submit** — Submit Form: https://www.pandaidx.com/docs/api/submit-form ### Visitors & Events - **POST /v1/auth/signup** — Sign Up Visitor: https://www.pandaidx.com/docs/api/visitor-signup - **POST /v1/auth/login** — Log In Visitor: https://www.pandaidx.com/docs/api/visitor-login - **POST /v1/auth/logout** — Log Out Visitor: https://www.pandaidx.com/docs/api/visitor-logout - **POST /v1/auth/refresh** — Refresh Visitor Token: https://www.pandaidx.com/docs/api/visitor-refresh - **GET /v1/auth/me** — Get Visitor Profile: https://www.pandaidx.com/docs/api/visitor-me - **POST /v1/auth/ott** — Create One-Time Token: https://www.pandaidx.com/docs/api/visitor-one-time-token - **POST /v1/auth/request-password** — Request Password Reset: https://www.pandaidx.com/docs/api/visitor-request-password - **POST /v1/auth/verify-email** — Verify Reset Code: https://www.pandaidx.com/docs/api/visitor-verify-email - **POST /v1/auth/reset-password** — Reset Visitor Password: https://www.pandaidx.com/docs/api/visitor-reset-password - **POST /v1/auth/google/exchange** — Exchange Google Token: https://www.pandaidx.com/docs/api/visitor-google-exchange - **PATCH /v1/account** — Update Visitor Account: https://www.pandaidx.com/docs/api/update-account - **POST /v1/account/photo** — Upload Account Photo: https://www.pandaidx.com/docs/api/upload-account-photo - **POST /v1/analytics/track** — Track Event: https://www.pandaidx.com/docs/api/track-event **Data standards:** - Listing fields follow RESO naming with PascalCase (ListPrice, BedroomsTotal, and so on) - All responses are JSON; dates are ISO 8601 - Errors are a JSON object with a `message` (403 with code TENANT_INACTIVE when the account is inactive); 429 includes Retry-After --- ## Widgets: React components for real estate websites (`@pandaidx/widgets` 1.20.0) The components behind every Panda IDX website, for any Next.js 16 / React 19 site: IDX property search, listing pages, condo directories and building pages, new developments, home valuation, lead forms, popups, visitor sign-in, accounts and saved searches, blog and agent pages. Each one renders complete in one line or comes apart into a root, parts, headless hooks and typed server loaders; Panda keeps the data, the MLS compliance and the lead routing. Docs: https://www.pandaidx.com/docs/widgets Install: npm install https://github.com/pandaidx/panda-widgets/releases/download/v1.20.0/pandaidx-widgets-1.20.0.tgz ## PandaProvider (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/panda-provider Status: Foundation - PandaProvider (import from "@pandaidx/widgets/client"): Root of every widget: tenant public key, API origin, visitor session, auth dialog, user drawer and the theme (--panda-* tokens on a layout-neutral [data-panda-root]; @panda/ui variable aliases only inside widget roots and the overlay container). - PandaOpen (import from "@pandaidx/widgets/client"): Sets how things open (open designs: listing, building, development, auth, account, collection, collectionPicker) for everything inside it, over . Anatomy: ```tsx ``` ## Integrations and analytics (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/integrations Status: Foundation - PandaIntegrations (import from "@pandaidx/widgets/client"): Mandatory headless global host, once directly inside PandaProvider next to PandaAnalytics. - PandaIntegrationPlacement (import from "@pandaidx/widgets/client"): Headless WhatsApp/Telegram binding. - PandaIntegration (import from "@pandaidx/widgets/client"): Headless binding to an AI-declared integration of any kind: content, contact menu, popup, embed or custom SDK. - PandaAnalytics (import from "@pandaidx/widgets/client"): Panda site analytics, shown in the owner's dashboard (Analytics): a page_view on load and on every client navigation (pathname change, via usePathname), with UTM parameters and the landing referrer; listing_view when a listing detail opens; likes, saved searches and collection adds of signed-in visitors (property_like, property_unlike, property_save_search, property_collection_add); and custom… Server loaders (@pandaidx/widgets/server): - fetchSiteRuntime: Read live runtime settings without caching. Anatomy: ```tsx ``` ## Property Search (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/property-search Status: Fully headless - PropertySearch (import from "@pandaidx/widgets/client"): Full IDX property search: location autocomplete, map search (drag / draw), sort, filters, listing cards, pagination, like/save/share gated by the visitor session, and the listing detail dialog. - PropertySearchRoot (import from "@pandaidx/widgets/client"): Root of a property search you lay out yourself: the same data, query, URL sync, card design (card), detail dialog (detail), opening (open) and ?listing= deep link as PropertySearch, with no layout. Roots: PropertySearchRoot Parts: SearchHeader, SearchFilters, SearchResultsHeader, SearchResults, ListingRow, ListingMlsBadge, ListingActionsMenu, SearchPanel, SearchPanelList, SearchPanelDetail, SearchPanelBack, SearchMap, SearchDisclaimers, SearchMobile, ListingCard, FilterLocation, FilterStatus, FilterType, FilterPrice, FilterBedsBaths, FilterSaleRent, FilterSort, FilterMore, FilterSaveSearch Required parts (render them at every level): SearchDisclaimers Hooks: - useListingActions: { signedIn, liked, likePending, toggleLike(), openCollections(), share(), openMortgage(), videoUrl, openVideo(), mlsSheetUrl, detailHref, openDetail(), available(action) } for one listing: a search row (`_id`, `ListingId`, `OriginatingSystemKey`, `ListPrice`, `image`, `VirtualTourURLUnbranded`) or a `getSearchResults` item as is (`_id`, `id`, `feed`, `photos`, `listPrice`, `videoUrl`). Dialogs open from the root's `ListingActionsHost`. `share(onOpen)` calls your `onOpen` instead of the Panda dialog and `shareData` gives its `{ url, title, image }` (build the dialog with `useShare`). Client component only. - useListingPanel: { listing, isOpen, loading, open(listing), back() } — the in-panel detail: `open` slides the panel to a listing (a search row or `useListingActions` listing), `back` returns to the list. Import from @pandaidx/widgets/client; inside `SearchPanelDetail` use `usePropertyOverview()` / the detail parts for the listing's data. - usePropertySearch: { listings (raw rows, for ListingCard), cards: SearchResultListing[] ({ _id, id, feed, markerKey, path, title, address, price (formatted, lease qualifier), listPrice, beds, baths, livingArea, status, forSale, photos, coordinates, courtesy (MLS rule: render it on every card), videoUrl }: the current page typed for your own cards), total, limit (page size), loading, query, search(filters), clear(), page (0-based), pageCount, goToPage(page), mapView, toggleMapView(), highlighted, highlight(key) (pin sync: `highlight(card.markerKey)` on pointer enter, `highlight(false)` on leave, `highlighted === card.markerKey` marks the card), sortOptions ({ value, label }[] = SEARCH_SORT_OPTIONS: `-listdate` Newest Listings (default), `listprice` Lowest Price, `-listprice` Highest Price, `beds` Number of Beds, `baths` Number of Baths), propertyTypes ({ group: "sale" | "rent", type, label, description, subtypes: { label, value }[] }[] in the visitor's language) } — import from @pandaidx/widgets/client. Open a card's listing in the root's detail (dialog, sheet, panel or page per `open`) with `useListingActions(card).openDetail()` (it also gives like / share / collection); the card's `path` is the Panda detail route. - useSearchFilter: useSearchFilter(key) → { value, set(value), clear() } for one query key (`minprice`, `maxprice`, `minbeds`, `maxbeds`, `minbaths`, `status`, `group` sale | rent (switches type + subtypes), `subtypes`, `sort`, `pool`, `waterfront`…): chips, sliders or toggles of your own; each `set` searches (debounce sliders / typed amounts), `clear()` goes back to the default (`status` Active, `group` sale) Keys and values for your own pills: `group` "sale" | "rent" (set switches `type` to Residential / Residential Lease and clears `subtypes`), `status` "Active" (default) | "Pending" | "Closed", `type` a `usePropertySearch().propertyTypes[].type` ("Residential", "Residential Lease", "Residential Income", "Land", "Commercial Sale"…: set it with `search({ type, subtypes: [] })`), `subtypes` string[] of that type's `subtypes[].value` ("Condominium", "Single Family Residence", "Townhouse"…), `minprice` / `maxprice` numbers (USD; rent: per month), `minbeds` / `minbaths` numbers (`maxbeds`, `maxbaths` too), `sort` one of `SEARCH_SORT_OPTIONS[].value`. Server loaders (@pandaidx/widgets/server): - fetchPropertySearchBootstrap: First page of listings + public application for the current URL (call in the page Server Component). - getSearchResults (typed data): Typed server search for listings you lay out yourself (a neighborhood landing, a "homes under $1M" strip, a static grid): same params as fetchPropertySearchBootstrap (query for a fixed search, searchParams, pageSize, sort). Anatomy: ```tsx ``` ## Property Detail (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/property-detail Status: Fully headless - PropertyDetail (import from "@pandaidx/widgets/client"): Listing page: action bar (save, collection, share), title, photos, overview + snapshot, map, details table, mortgage calculator and the schedule-a-tour / contact card. - PropertyDetailRoot (import from "@pandaidx/widgets/client"): Root of a Panda listing detail you lay out yourself: it holds the listing, the site, the design and the shared dialogs (Request Showing form, Contact Listing Agent, mortgage calculator, Add to Collection with sign-in), and tracks the listing view. Roots: PropertyDetailRoot Parts: PropertyDetailHeader, PropertyDetailHeading, PropertyDetailPrice, PropertyDetailActions, PropertyDetailGallery, PropertyDetailSections, PropertyDetailSection, PropertyFacts, PropertyRemarks, PropertyFinancial, PropertyFeatures, PropertyHighlights, PropertyWalkScore, PropertyLocationMap, PropertyDetailMap, PropertySchools, PropertyMortgage, PropertyDetailAgentCard, PropertyCompliance, PropertyDetailDisclaimer Required parts (render them at every level): PropertyCompliance Hooks: - useNearbyPlaces: useNearbyPlaces({ lat?, lng?, categories? }) → { categories: { key, label, color }[], active, setActive(key | null), places: { name, address, rating, lat, lng, photo… }[], loading, selected, select(place), coordinates } — your own "Around this home" list or chips inside PropertyDetailRoot (coordinates come from the listing); one cached request per category, nothing loads until setActive. Import from @pandaidx/widgets/client; never fetch /v1/nearby-places yourself. - usePropertyGallery: { photos: string[], count, title, alt(index), photoLoading(index) → { loading, fetchPriority? } (spread on each next/image: the first photo is the page's LCP, eager + high priority; the next four eager; the rest lazy), coordinates: [lng, lat] | null, openPhotos(index?), viewport: "desktop" | "mobile" } — import from @pandaidx/widgets/client; rebuild the photos your own way (its Map view: `PropertyDetailMap` in a box of the same height, kept mounted and cross-faded, so the switch does not move the page); openPhotos opens the detail's full-screen viewer (never mount a second viewer inside the root; the standalone `PhotoLightbox` export, controlled, is only for photos outside a listing detail) - usePropertyDetail: { listing, application, t, design, isOwner, offMarket, propertyUrl, openRequestShowing, requestShowingDialog: { open, onOpenChange } (bind your own dialog given as `parts.requestShowing`), openContactAgent, openMortgage, openCollections, openPhotos, closeDetail (closes the search dialog; null on a page) } - usePropertyFacts: { groups: { id: "facts" | "financial" | "exterior" | "interior" | "additional", title, facts: { key, label, value (formatted text), raw, column? }[] }[], group(id) } — every fact labelled in the site language and formatted, for cards, chips or your own tables - usePropertyOverview: { title, address, price, listPrice, previousListPrice, estimatedPayment, beds, baths, livingArea, status, statusInfo: { market: sale|rent, state: active|pending|closed|offmarket, standardStatus, closeDate, closePrice, tone: positive|warning|neutral } (build your own badge), forSale, remarks, highlights, photos, coordinates, directionsUrl, virtualTourUrl, compliance: { courtesy, feed, disclaimer }, openPhotos(i?), openRequestShowing(), openMortgage(), openCollections() } — rebuild the header / summary your own way Server loaders (@pandaidx/widgets/server): - fetchListingDetail: Listing + public application + request-showing form; returns null when the listing does not exist (call notFound()). - getListingDetail (typed data): Typed listing detail for a page you design yourself: detail (title, price, estimated payment, status, remarks, photos, coordinates, fact groups labelled in locale, compliance) + the raw listing / application / requestShowingForm for . Anatomy: ```tsx ``` ## Home Search (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/home-search Status: Headless hook - HomeSearch (import from "@pandaidx/widgets/client"): Homepage hero search of the Panda websites: For Sale / For Rent / Sold tabs over the pill autocomplete (cities, buildings, zip codes, addresses, MLS#) with the black round search button on desktop, and tabs + a pill that opens the fullscreen search dialog on phones. Hooks: - useHomeSearch: useHomeSearch({ searchPath?, markets?: ["sale","rent","sold"], initialMarket?, marketLabels?, placeholder?, minLength?: 1 }) → { markets: { id, label, active }[], market, setMarket(id), query, setQuery(value), options: { id, kind: "building" | "area" | "development" | "postalCode" | "address" | "unit" | "listing" | "smart" | "text", label, detail, image, raw }[] (grouped and limited like the Panda bar), open, activeIndex, setActiveIndex(i), loading, error, pending, placeholder, select(option) (navigates to the search page with the market's status/type, an MLS# to its page, and returns the URL), submit() (the highlighted option, else Panda's smart suggestion or first result for the typed text; Enter), close(), warm(), inputProps (spread on your : value, onChange, onKeyDown, onFocus, onBlur, placeholder and the combobox aria), listProps (spread on the list: id, role="listbox"), optionProps(option, index) (spread on each row: id, role="option", aria-selected, hover, click) } — the site's own hero search: tabs, field, suggestion list (with the photo of an area or building when `image`), button, error line and loading state in the site's style, on desktop and phones. Panda owns the autocomplete service, the catalog warm-up, the keyboard and the navigation; never call /v1/autocomplete or /v1/suggestions yourself and never read the Panda bar's markup with CSS. Client component only. Anatomy: ```tsx ``` ## Listing Grid (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/listing-grid Status: Root + parts - ListingGrid (import from "@pandaidx/widgets/client"): Listing grids of the Panda websites outside the search. Roots: ListingGridRoot Parts: ListingGridCard, ListingGridMap, ListingRow, ListingActionsMenu, ListingMlsBadge, MlsDisclaimers Required parts (render them at every level): MlsDisclaimers Hooks: - useListingGrid: { source: "agent" | "office" | "team" | "collection", status: "active" | "pending" | "active-under-contract" | "sold" | null, listings, total, page, pageSize, hasMore, collection: { name, description, path, totalCount } | null, application, isLiked(listing) } — the data of the nearest `ListingGridRoot`: your own title, status tabs (links to `?status=active|pending|sold`), count, empty state and page links (`hasMore`). Client component only. - useListingActions: { signedIn, liked, likePending, toggleLike(), openCollections(), share(), openMortgage(), videoUrl, openVideo(), mlsSheetUrl, detailHref, openDetail(), available(action) } for one grid listing (as is: `_id`, `ListingId`, `OriginatingSystemKey`, `ListPrice`, `image`…). The detail, collections, share, mortgage and video dialogs open from the root's `ListingActionsHost`. Client component only. Server loaders (@pandaidx/widgets/server): - fetchListingGrid: Listings of an inventory or a collection + the public application and request-showing form; null when the team member or collection does not exist (call notFound()). Anatomy: ```tsx ``` ## MLS Sheet (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/mls-sheet Status: Complete widget - MlsSheet (import from "@pandaidx/widgets/client"): The printable MLS sheet of a listing (Panda /mls//sheet, linked by the panda listing detail): Back to Listing / Print toolbar, photo + price + address header, General, Location, Rooms, Financial, Additional and Remarks sections, and the "Prepared by" footer with the site logo and the MLS disclaimer. Roots: MlsSheetRoot Parts: MlsSheetCompliance, MlsSheetPrint Required parts (render them at every level): MlsSheetCompliance Server loaders (@pandaidx/widgets/server): - fetchListingSheet: Listing (GET /v1/listings/:id?view=sheet: the detail fields plus the sheet's public RESO fields) + public application; null when the listing does not exist (call notFound()). - getListingSheet (typed data): Typed printable sheet for a page you design yourself: sheet = { title, address, price, mlsNumber, status, forSale, photo, photos, sections: [{ id, title, fields: [{ key, label, value, href? Anatomy: ```tsx ``` ## Condo Directory (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/condo-directory Status: Root + parts - CondoDirectory (import from "@pandaidx/widgets/client"): The condo directory (Panda /condos): area picker, building name search, status and sort, landing rows per area, building cards (live price ranges and counters) and the buildings map. - DirectoryHeader (import from "@pandaidx/widgets/client"): Headers of the Panda website directories. Parts: PandaDirectoryRoot, DirectoryFilterBar, DirectorySearchName, DirectoryFilterAreas, DirectoryFilterPrice, DirectoryFilterStatus, DirectoryFilterBedsBaths, DirectoryFilterType, DirectoryMoreFilters, DirectoryResultsHeader, DirectoryCount, DirectorySort, DirectoryDisplayToggle, DirectoryLoadMore, DirectoryFilterYear, DirectoryFilterUnits, DirectoryFilterFloors, DirectoryFilterSize, DirectoryResults, DirectoryMap, CondoAreaMap Hooks: - useCondoDirectory: useCondoDirectory({ data, initialFilters?, syncUrl?: true, pins?: false }) → { buildings: { id, slug, type: "buildings", href, query, name, path, links, headline, city, address, image, location, price, rentPrice, beds, baths, sqft, activeListings… }[] (current page, live; each card is a data-link record), pins: { id, slug, kind, name, path, location, image, price }[] | null (with `pins: true`, also on `fetchCondoDirectory({ pins: true })`: every matching building with coordinates, max 500, for ``), groups: { area, slug, totalCount, buildings }[] (landing rows; only page 1 with no filters), areas: { slug, name, buildingCount }[], total, page, pageSize, totalPages, query: { area, city, q, status: "forSale" | "forRent" | null, minPrice, maxPrice, minBeds, minBaths, types, features, sort… }, filtered, loading, searchText, search(text) (name box, debounced), update(change) (merges filters, back to page 1), setPage(page), reset() } — `data` comes from `fetchCondoDirectory`. Same live data, URL names and syncing as ``: library links such as `/condos?area=aventura` land filtered. Your own filter bar, cards (link each with `resolveLibraryHref(building, "default", { buildingDetail: "/condos/{slug}" })` from @pandaidx/widgets/search: the card is the unchanged API record; never `building.path` or a rebuilt URL), pager and map (`CondoAreaMap`) in the site's style. Client component only; never call /v1/condos yourself. - usePandaDirectory: usePandaDirectory() (inside PandaDirectoryRoot) → the websites directory state: { query (websites names: status, selectedAreas, searchName, priceRange, bedsBaths, sqftRange, propertySubTypes, amenities, views, features, yearBuiltRange, storiesRange, unitsRange, country, sort), handleSubmit(change), total, isLoading, isLoadingMore, hasMore, loadMore(), areasHasMore, loadMoreAreas(), viewMode (split | fullList | fullMap), setViewMode, displayMode, setDisplayMode… } plus the results as typed records: cards: Card[] (`SiteBuildingCard` on condos, `SiteNewDevelopment` on new developments, the same fields as useCondoDirectory / useNewDevelopmentsDirectory; link each with `resolveLibraryHref(card, "default", { buildingDetail: "/condos/{slug}" })`), areaRows: { area, slug, totalCount, cards }[] (the landing rows per area, condos and new developments: the first projects of each area, from the first paint), landing (true = no filter is set: draw `areaRows`, else `cards`), hoveredId / setHoveredId(id) (map hover sync with DirectoryMap, `card.id`), developers (new developments: `{ name, count }[]`, A to Z; filter with `handleSubmit({ developer: name })`), open(card) (the root's dialog / sheet / page), mapCards (every map pin as a typed card with `location`, price, photos and developer: draw your own map with any engine) and searchMapArea(points, { drawn? }) (search a viewport box or a drawn ring, like DirectoryMap) and facets ({ areas: Record, developers: { name, count }[] } | null: what picking each area or developer lists under the OTHER filters on screen, from the same search as the list, so `facets.areas["AVENTURA"]` (keys are the upper-case `area.query`) is exactly the total you get after choosing Aventura, also with price, beds or delivery year set; `developers` only on new developments. Null before the first search and on the landing with no filter: fall back to `allAreas[].buildingCount` and `developers[].count` then). Enough to draw the results, and even the map, 100% yourself. Server loaders (@pandaidx/widgets/server): - fetchCondoDirectory: First page of GET /v1/condos, filtered by the page URL (websites or API names) over initialFilters. - fetchPandaCondoDirectory: Data of variant="panda" (GET /v1/condos/directory?mode=condo): every area, the unfiltered first paint (landing rows + map pins) when the URL has no filters, the public application and the request-information form. Anatomy: ```tsx ``` ## Building Detail (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/building-detail Status: Root + blocks - BuildingDetail (import from "@pandaidx/widgets/client"): A condo building page (Panda /condos/--): photo gallery, description, facts and sales stats, amenities, the listings inside by status (for sale / for rent / sold, IDX cards with like, collections and the detail dialog), location map and a lead form (request-showing spot). Roots: BuildingDetailRoot Parts: BuildingDetailBlock, BuildingListingsStatusTabs, BuildingListingsToolbar, BuildingListingsResults, BuildingListingCard, BuildingListingsHeading, BuildingAmenityList Hooks: - useBuildingDetail: { building (amenities, features, salesStats, hoa, units…), listings, application, leadForm, displayName, address, cityHref, photos, agent, status, setStatus, openRequest(), goToListings(status), downloadSheet(), amenityData, amenityRows { building, additional }: { key, label, icon, value, short }[], stats, details (key details: label + value), priceRange, t } — import from @pandaidx/widgets/client; inside BuildingDetailRoot or the `parts` of BuildingDetail variant="panda" - useBuildingListings: { statuses, counts, status, selectStatus(s), statusInfo { closed, group }, filters, bedsTab, setBedsTab, bedOptions, unitFilter, setUnitFilter, bathsMin, setBathsMin, bathOptions, priceRange { min, max }, setPriceRange(patch), priceSteps, sort, chooseSort(s), sortOptions, view, chooseView(v), views, listings, filtered (draw these), hasMore, loading, loadMore(), openListing(listing), listingHref(listing), statusLabel(listing), unitLabel(listing), isRentGroup(listing) } — the units browser headless; inside BuildingDetailRoot or NewDevelopmentRoot Server loaders (@pandaidx/widgets/server): - fetchBuildingDetail: Building (GET /v1/buildings/:slug?view=page, with the Panda website's page data in page), its first for-sale page, the public application and the lead form; null when unknown (call notFound()). - fetchBuildingDetail (typed data): Typed building for a page you design yourself: render it inside (Request Information, listings tab, printable sheet) with BuildingDetailBlock id blocks or useBuildingDetail(). Anatomy: ```tsx ``` ## Condo Area (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/condo-area Status: Root + parts - CondoArea (import from "@pandaidx/widgets/client"): One condo area (Panda /area/): hero with description, market counters, price stats, neighborhood scores, the area outline map and its buildings with paging. Parts: CondoAreaMap Hooks: - useCondoArea: useCondoArea({ data }) → { area: { slug, name, image, description, boundary… }, paragraphs (the description), market: { key, label, today, value, change, changeText }[] (For Sale, For Rent, Pending, Sold…; zeros left out), stats: { label, value }[] (formatted averages, price ranges and counts; empty ones left out), scores: { label, score, rating }[] (Walk, Bike, Transit), highlights: { label, text }[] (restaurants, parks…), buildings (current page; link each with its `path`), total, page, pageSize, totalPages, setPage(page), loading } — `data` comes from `fetchCondoArea` (null → `notFound()`). `setPage` loads the buildings of another page in place (the previous page stays in `buildings` while it loads). Draw the hero, counters, stats, scores and building cards in the site's style; `CondoArea` stays the ready-made page. Client component only. Server loaders (@pandaidx/widgets/server): - fetchCondoArea: GET /v1/condos/areas/:slug (page from the URL); null for an unknown area. - fetchPandaCondoArea: Data of variant="panda" (GET /v1/condos/directory/area/:slug): the area, the directory areas, the last market totals, the public application and the request-information form; null for an unknown area (notFound()). Anatomy: ```tsx ``` ## New Developments (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/new-developments Status: Root + parts - NewDevelopments (import from "@pandaidx/widgets/client"): Pre-construction directory (Panda /new-developments): country, city, status, price and name filters, landing rows per area, project cards (developer, units, asking range) and the map. Parts: PandaDirectoryRoot, DirectoryFilterBar, DirectorySearchName, DirectoryFilterAreas, DirectoryFilterPrice, DirectoryFilterCountry, DirectoryResultsHeader, DirectoryCount, DirectorySort, DirectoryDisplayToggle, DirectoryLoadMore, DirectoryFilterYear, DirectoryFilterUnits, DirectoryFilterFloors, DirectoryFilterSize, DirectoryFilterDeveloper, DirectoryResults, DirectoryMap, NewDevelopmentsMap Hooks: - useNewDevelopmentsDirectory: useNewDevelopmentsDirectory({ data, initialFilters?, syncUrl?: true }) → { newDevelopments: { id, slug, type: "newDevelopments", href, query, name, path, links, city, developer, units, yearBuilt, price, area, images: { cover, gallery }, activeListings… }[] (current page), groups: { area, slug, totalCount, newDevelopments }[] (landing rows; only page 1 with no filters), countries: { code, name, count }[], total, page, pageSize, totalPages, query: { country, city, status: "forSale" | "forRent" | null, minPrice, maxPrice, q }, filtered, loading, searchText, search(text) (name box, debounced), update(change) (merges filters, back to page 1), setPage(page), reset() } — `data` comes from `fetchNewDevelopments`. Same live data, URL names and syncing as ``. Your own filters, cards (link each with `resolveLibraryHref(development, "default", { newDevelopmentDetail: "/new-development/{slug}" })` from @pandaidx/widgets/search; never `development.path`), pager and map (`NewDevelopmentsMap`) in the site's style. There is no sort: the API lists projects by name. Client component only; never call /v1/new-developments yourself. - usePandaDirectory: usePandaDirectory() (inside PandaDirectoryRoot) → the websites directory state: { query (websites names: status, selectedAreas, searchName, priceRange, bedsBaths, sqftRange, propertySubTypes, amenities, views, features, yearBuiltRange, storiesRange, unitsRange, country, sort), handleSubmit(change), total, isLoading, isLoadingMore, hasMore, loadMore(), areasHasMore, loadMoreAreas(), viewMode (split | fullList | fullMap), setViewMode, displayMode, setDisplayMode… } plus the results as typed records: cards: Card[] (`SiteBuildingCard` on condos, `SiteNewDevelopment` on new developments, the same fields as useCondoDirectory / useNewDevelopmentsDirectory; link each with `resolveLibraryHref(card, "default", { buildingDetail: "/condos/{slug}" })`), areaRows: { area, slug, totalCount, cards }[] (the landing rows per area, condos and new developments: the first projects of each area, from the first paint), landing (true = no filter is set: draw `areaRows`, else `cards`), hoveredId / setHoveredId(id) (map hover sync with DirectoryMap, `card.id`), developers (new developments: `{ name, count }[]`, A to Z; filter with `handleSubmit({ developer: name })`), open(card) (the root's dialog / sheet / page), mapCards (every map pin as a typed card with `location`, price, photos and developer: draw your own map with any engine) and searchMapArea(points, { drawn? }) (search a viewport box or a drawn ring, like DirectoryMap) and facets ({ areas: Record, developers: { name, count }[] } | null: what picking each area or developer lists under the OTHER filters on screen, from the same search as the list, so `facets.areas["AVENTURA"]` (keys are the upper-case `area.query`) is exactly the total you get after choosing Aventura, also with price, beds or delivery year set; `developers` only on new developments. Null before the first search and on the landing with no filter: fall back to `allAreas[].buildingCount` and `developers[].count` then). Enough to draw the results, and even the map, 100% yourself. Server loaders (@pandaidx/widgets/server): - fetchNewDevelopments: First page of GET /v1/new-developments/directory, filtered by the page URL (country, city / area, status, minprice / minPrice, maxprice / maxPrice, building / q, page) over initialFilters. - fetchPandaNewDevelopments: Data of variant="panda" (GET /v1/condos/directory?mode=newdev): areas, countries, the unfiltered first paint when the URL has no filters, the public application and the request-information form. Anatomy: ```tsx ``` ## New Development Detail (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/new-development-detail Status: Root + blocks - NewDevelopmentDetail (import from "@pandaidx/widgets/client"): A pre-construction project page (Panda /new-development/): gallery, description, brochure and video, specs (asking prices, sizes, units, developer, architect), amenities, floor plans, deposit schedule, resale listings inside, map and a lead form (new-development spot). Roots: NewDevelopmentRoot Parts: NewDevelopmentBlock Hooks: - useNewDevelopmentDetail: { newDevelopment, listings, application, leadForm, displayName, address, photos, photoAlt(i), stats: { label, value }[], keyDetails: { label, value }[], deposits: string[], highlights: string[], amenities: { amenities, features }, amenityRows { building, additional } (draw with BuildingAmenityList), downloads: { brochure, floorplans }, downloadLink(href, label, icon?) (behind sign-up), openRequest(), openPhotos(i?), openVideo() | null } — import from @pandaidx/widgets/client; inside NewDevelopmentRoot or the `parts` of NewDevelopmentDetail variant="panda" - useBuildingListings: The project's units (for sale and for rent in one list) headless: { filtered, listings, bedsTab, setBedsTab, bedOptions, unitFilter, setUnitFilter, bathsMin, setBathsMin, sort, chooseSort, sortOptions, view, chooseView, openListing(listing), statusLabel(listing), unitLabel(listing), isRentGroup(listing) } — draw them with BuildingListingCard, BuildingListingsToolbar and BuildingListingsResults, or your own markup Server loaders (@pandaidx/widgets/server): - fetchNewDevelopmentDetail: Project (GET /v1/new-developments/:slug) with its first listing pages, the public application and the lead form; null when unknown (call notFound()). - fetchNewDevelopmentDetail (typed data): Typed project for a page you design yourself: render it inside (Request Information, viewer, video, sign-up-gated downloads) with blocks or useNewDevelopmentDetail(); your own markup between the blocks (and parts.hero / parts.gallery) renders outside the widget… Anatomy: ```tsx ``` ## Home Valuation (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/home-valuation Status: Fully headless - HomeValuation (import from "@pandaidx/widgets/client"): The Panda website "How much is my home worth" flow (/how-much-is-my-home-worth), complete and designable (design: colors, background, shape, address bar, report layout; a CMA page with no lead form is MarketAnalysis, not this widget): an address pill with Google predictions (GET /v1/places/autocomplete, the key stays on the API), the comparable-sales "Panda Estimate" over the tenant's own MLS… - MarketAnalysis (import from "@pandaidx/widgets/client"): A comparative market analysis (CMA) of one home, and nothing else: the Panda Estimate with its low/high range and confidence, the market snapshot and $/sq ft trend and distribution, the home's sale history, the comparable sales with a map of them around the home, and Share. Roots: HomeValuationRoot, MarketAnalysis Parts: ValuationSearch, ValuationLeadForm, ValuationReport, ValuationSteps, ValuationSearchInput, ValuationReportHeader, ValuationEstimateCard, ValuationNoEstimate, ValuationMarketSection, ValuationMarketStats, ValuationTrendChart, ValuationHistogram, ValuationSaleHistory, ValuationCompsMap, ValuationComps Required parts (render them at every level): HomeValuationRoot Hooks: - useHomeValuation: { step: "search" | "form" | "result", data, pick(data), reset(), goBack(), selectComp(comp), shareUrl, busy, labels, reportLabels, gate } — import from @pandaidx/widgets/client - useValuationReport: null outside `` / before a result, else { valuation: { address, kind, subject { bedrooms, bathrooms, livingArea, yearBuilt, propertySubType, saleHistory[] }, estimate { value, low, high, pricePerSf, confidence, compsUsed } | null, market { label, sales, months, medianPricePerSf, p25PricePerSf, p75PricePerSf, trend[], histogram[] } | null, comps[] , reason }, labels, formatCurrency(n), formatNumber(n), formatDate(iso), onCompSelect, emptyState, subjectFacts } — inside `` children: draw any report block your own way - useAddressSearch: useAddressSearch({ href, minLength?: 3, debounce?: 200 }) → { query, setQuery(value), suggestions: { placeId, address }[] (up to 5), loading, available, pending, select(suggestion) (navigates to `href?placeId=&unit=` and returns the URL; a unit typed in `query` rides along), submit() (opens the first suggestion: Enter) } — the site's own address input and suggestions list over Google predictions (the key stays on the API); `href` is the route of the page that renders ``. Client component only; never fetch /v1/places/autocomplete yourself. Server loaders (@pandaidx/widgets/server): - fetchHomeValuation: The estimate of a shared link (GET /v1/home-valuation?listingId= or ?placeId=&unit=) from the page's searchParams; null when the URL has neither or it fails (never throws). - getHomeValuation (typed data): Typed estimate of an MLS listing (listingId) or a Google place (placeId + unit), or of a shared link (searchParams). Anatomy: ```tsx ``` ## Market Pulse (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/market-pulse Status: Complete widget - MarketPulse (import from "@pandaidx/widgets/client"): Live market of several areas side by side ("Market pulse"), over the site's own MLS feeds and refreshed every hour: homes for sale with the change vs last week, the market type (seller's under 4 months of supply, buyer's over 7), the medians of the last three months of closings (sale price, $/sq ft, days on market, sale-to-list), months of supply, closings of the last 30 days with their change,… Server loaders (@pandaidx/widgets/server): - fetchMarketPulse: GET /v1/market (each area's snapshot, changes and the cma.area of its prefilled CMA, over the site's MLS feeds; cached an hour). - fetchMarket (typed data): One area's market (GET /v1/market/:slug) for a design of your own: { area: { name, slug, query }, asOf, type, snapshot: { active, pending, sold7, sold30, sold90, medianSalePrice, medianPricePerSqft, medianDaysOnMarket, saleToListPct, monthsOfSupply, marketType }, changes: { activeWeekPct,… Anatomy: ```tsx ``` ## Forms (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/forms Status: Fully headless - PandaForm (import from "@pandaidx/widgets/client"): A Panda dynamic form (contact, home valuation, request showing, new development, or any form by id) with the websites field renderers. Roots: PandaFormRoot Parts: FormFields, FormField, FormStep, FormProgress, FormSubmit, FormBack, FormActions, FormLegal, FormSuccess Hooks: - usePandaForm: { form, fields, stepFields, values, setValue(id, value), errors, locked (fields filled from the signed-in visitor), step (0-based), stepCount, stepInfo ({ step, title?, description?, image? } the form gave the step on screen; image = the https URL the owner picked for it), isLastStep, next(), back(), submit(), submitting, submitted, failure, submitText, successMessage, download } — your own inputs with the same validation and the same lead submit - usePandaFormWarmup: nothing: call usePandaFormWarmup({ spot }) (or { formId }) in the component that holds your own closed dialog with a PandaFormRoot; the form's code and schema load after the visitor's first interaction (never during the page load), so the dialog opens complete at its final height (no growth when the form arrives) Server loaders (@pandaidx/widgets/server): - fetchForm: The form of a page spot (GET /v1/forms/:spot) or by id (GET /v1/forms/by-id/:id); null when none. - fetchForm (typed data): The form definition (rows of fields with type, label, required, CRM mapping, options, step) for or . Anatomy: ```tsx ``` ## Contact Page (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/contact-page Status: Complete widget - ContactPage (import from "@pandaidx/widgets/client"): The Panda websites /contact page (render it without site chrome): the contact image full height on one side and, on the other, the form assigned to the contact spot with its name and description centered above it (PandaForm in the websites form look), the dashboard empty state when none is assigned, and an X back to the homepage. Roots: PandaFormRoot Server loaders (@pandaidx/widgets/server): - fetchContactPage: The form of the contact spot (/v1/forms/contact) and the side image (homepage.contactImage, else the owner's headshot). Anatomy: ```tsx ``` ## Popups (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/popups Status: Fully headless - PandaPopups (import from "@pandaidx/widgets/client"): The website's popups (Popups in the dashboard, manage_popups), with the Panda website behavior: page targeting (/, /*, /listing/*, exact paths; a leading locale is ignored), trigger (delay in seconds, scroll depth, exit intent, a click on a selector, every link to a site path such as /contact, after N different listings opened (views, the registration wall: a sign-up popup that is not… Roots: PandaPopupsRoot Parts: PopupFrame, PopupForm, PopupAuth, PandaPopupsDesign Hooks: - usePandaPopups: { active: WidgetPopup | null ({ id, key, type: "form" | "auth" | "content", mode, form, pages, delay, trigger: { kind: "delay" | "scroll" (percent) | "exit" | "click" (selector) | "link" (href) | "manual" }, frequency, dismissable }), dismiss(), complete(), trigger(idOrKey) } — your own popup surface; `data-panda-popup=""` opens a popup from any element Server loaders (@pandaidx/widgets/server): - fetchPopups: The tenant's enabled popups with their targeting (GET /v1/popups); [] when none. - fetchPopups (typed data): The website's enabled popups (dashboard → Popups) with their key, trigger, pages and frequency: the popups prop of . Anatomy: ```tsx ``` ## Sign in (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/sign-in Status: Root + parts - PandaSignIn (import from "@pandaidx/widgets/client"): Panda visitor sign-in rendered inline (not a dialog): the same panels, API calls and session as the provider's auth dialog (email + password, Continue with Google, sign-up with phone + consent, forgot / reset password), styled by the theme (dialog, input and button tokens). - PandaAuthRoot (import from "@pandaidx/widgets/client"): Root of a sign-in flow you lay out yourself: one part per step (login, sign-up, forgot password, 6-digit code, new password), the Panda handlers (session, Google, consent, reset by link or code) and the PandaSignIn panel design, no container. - PandaAuthButton (import from "@pandaidx/widgets/client"): Header account entry: signed out it opens the auth dialog (styled by the theme); signed in the avatar opens the account menu (collections, saved searches, likes, My Account, sign out). - PandaAuthCallback (import from "@pandaidx/widgets/client"): Google sign-in return page: render it at /auth/callback; it exchanges ?ott= for the visitor session and redirects. Roots: PandaAuthRoot Parts: AuthStep, AuthWhen, AuthLogin, AuthSignup, AuthForgotPassword, AuthVerifyCode, AuthResetPassword, AuthTabs, AuthGoogle, AuthDivider, AuthBackLink, AuthLegal Hooks: - usePandaAuth: { user, signedIn, openAuth("login" | "signup"), openDrawer(tab?), logout() } — import from @pandaidx/widgets/client; your own sign-in links, gates and account menus (sign-in opens the site's way: `PandaProvider open.auth`) - usePandaAuthFlow: usePandaAuthFlow({ redirectTo? }) → { login({ email, password }), signup({ name, email, phone, password, marketingConsent: true }), loginWithGoogle(), signupWithGoogle({ phone, marketingConsent }), requestReset(email) (email with link + 6-digit code), verifyCode(email, code) → { ok, token }, resetPassword(token, password, confirmPassword), pending } — each resolves { ok, message, errors }; your own login / sign-up / reset forms over the Panda session. A sign-up of your own shows a consent checkbox (publish checks it) and the Privacy / Terms links - usePandaAuthForm: usePandaAuthForm({ defaultMode?, modes?, redirectTo?, initialValues?, initialToken? }) → { mode, setMode(mode), modes, fields (of the step), values, setValue(field, value), field(name) → props for your (name, value, onChange, autoComplete, aria-invalid), errors ({ field: message, form: server message }), consent { checked, setChecked, copy, companyName, privacyLink, termsLink, error }, submit(event?) (runs the step: login, sign-up, send code → verify-token, verify → reset-password, new password), loginWithGoogle(), signupWithGoogle() (checks phone + consent first), forgotPassword(), backToLogin(), pending } — a sign-in fully of your own markup (any order: Google first, no tabs, your title), same session and rules as the dialog. Sign-up must render `consent.copy` beside a checkbox bound to `consent.checked`, with Terms / Privacy linked Anatomy: ```tsx ``` ## Account and saved searches (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/account Status: Root + parts - PandaAccountRoot (import from "@pandaidx/widgets/client"): The visitor account area (collections, saved searches, likes and the visitor's own profile) in its own page (sections in a left sidebar), a dialog-sidebar or the drawer. - PandaAccountMenu (import from "@pandaidx/widgets/client"): The signed-in visitor's account menu: My Collections, Saved Searches, Likes (opened the PandaProvider open.account way), My Account, Dashboard (site owner only) and Sign Out, translated by the widget dictionary. - PandaAccountProfile (import from "@pandaidx/widgets/client"): The visitor's "My Account" on the site: photo (remove, or a photo URL with ProfilePhoto allowUrl), name and phone numbers, email read only, saved with the visitor session (PATCH /v1/account, the websites Edit Profile update: CRM activity and owner notification). - CollectionPicker (import from "@pandaidx/widgets/client"): Add-to-collection picker for your own dialog, popover, sheet or page: the visitor's collections with a check on the ones holding the listing (click adds / removes), and Create Collection with the listing in it, over the same services as the websites dialog. Roots: PandaAccountRoot, PandaAccountMenu, PandaAccountProfile, CollectionPicker Parts: AccountTabs, AccountCollections, AccountCollectionView, AccountSavedSearches, AccountLikes, AccountProfile, AccountCard, AccountMenuItem, AccountMenuHeader, AccountMenuSeparator, ProfilePhoto, ProfileFields, ProfileSave Hooks: - useVisitorLibrary: { collections: { _id, name, slug, images, count }[], savedSearches: { _id, title, url, image, total }[], likes: { ListingId, address, image, ListPrice… }[], counts: { collections, saved, likes }, loading, signedIn, refresh(), deleteCollection(id), renameCollection(id, name), deleteSavedSearch(id), removeLike(listing), collectionListings(id) } — counters, cards or pages of your own (same cache as the drawer) - usePandaAuth: { user, signedIn, openAuth(), openDrawer(tab?), logout() } — a menu fully of your own - useAccountProfile: { profile: { name, phones, image }, email, setField(field, value), save() → { ok, message }, uploadPhoto(file) → { ok, message } (sets `image`; save after), uploading, reset(), saving, error, saved, dirty, signedIn } — a profile form of your own - useCollectionPicker: useCollectionPicker(listing, { enabled? }) → { collections: { _id, name, image, count, selected }[], loading, error, signedIn, toggle(collectionId), create(name), creating } — a picker of your own Anatomy: ```tsx ``` ## Like and Share (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/like-and-share Status: Headless hook - LikeButton (import from "@pandaidx/widgets/client"): The websites listing heart for custom listing cards: signed-out visitors get the sign-up dialog; signed-in visitors like / unlike the listing (their account, the visitor drawer and the owner's CRM activity). - ShareButton (import from "@pandaidx/widgets/client"): The Panda share button + dialog (listings, buildings, areas, collections, stories): preview photo and name, Copy Link, Email, WhatsApp, Facebook, LinkedIn, Telegram and X. Roots: LikeButton, ShareButton Hooks: - useLike: useLike(listing) → { liked, toggle(), pending, signedIn } — your own heart / save control (signed out, toggle opens sign-up); never store favorites yourself - useShare: useShare({ url?, title?, image?, context? }) → { url, title, image, channels: { id, label, href, open() }[], copy(): Promise, copied, native, nativeShare() } — your own share dialog or sheet; every action reports the `share` analytics event, so never open window.open / mailto links or write navigator.clipboard yourself Anatomy: ```tsx ``` ## Home Cover (@pandaidx/widgets 1.20.0) URL: https://www.pandaidx.com/docs/widgets/home-cover Status: Headless hook - HomeCover (import from "@pandaidx/widgets/client"): Homepage hero of the Panda websites (the original cover): the cover photo (phone cover on phones) or the plan's looping background video, the hero video play button, the owner portrait on phones and the centered HomeSearch (websites pill design: For Sale / For Rent / Sold tabs over the pill autocomplete). Hooks: - useHomeCover: useHomeCover({ data }) → { cover, coverMobile (show it below `sm`, the desktop cover from `sm` up), backgroundVideo (looping MP4 for a `