Property Listings Integration on NestSeekers Australia

NestSeekers Australia — Property Listings Integration Site: nestseekersaustralia.com.au (WordPress + Elementor) Objective Build a custom property listings feature on the site that: Pulls live listing data from the MantisProperty CRM via their API (reference: MantisPropertyAPI_XMLSpec.pdf). Displays listings styled to match the existing site design (not MantisProperty's default UI). Gives each listing its own real, crawlable WordPress URL on the site's own domain — not an iframe, not a JavaScript-only overlay. Shows a featured-properties carousel on the homepage. Captures buyer enquiries reliably. Scope of work Data sync Connect to the MantisProperty API using account credentials (to be provided). Pull listing data on a scheduled basis (e.g. WP-Cron) — address, price/status, bedrooms/bathrooms/car spaces, description, photos, agent details, listing status (For Sale / Under Offer / Sold, etc.). Store each listing as a native WordPress entry (custom post type) — not just cached data rendered on the fly — so each listing gets a real, indexable URL. Status must always be a single source of truth per listing — a listing must never be able to display two conflicting statuses (e.g. "Sold" and "For Sale") at once. Handle image imports cleanly: full-resolution photos, no stretching/cropping artefacts. Confirm whether the API serves clean images or images with a watermark baked in; if the latter, flag before proceeding further. Property listing page template One template, used for every property, styled to match the existing Elementor site (typography, colours, header/footer, layout language). Each listing has its own unique URL. Include: photo gallery, address, price/status, bed/bath/car, description, enquiry form. Page title and meta description generated per listing from the listing data. Featured properties carousel Use Elementor Pro's native Loop Carousel widget, pulling from the custom post type above. Placement: homepage, reusable elsewhere if needed. Enquiry capture Enquiry form on each property page. Submissions should post back into MantisProperty via the API so they land in the MantisProperty CRM inbox. If this isn't feasible via the API, flag it and fall back to direct email delivery. Enquiry submissions must not fail silently — confirm handling if the API is unreachable at submission time. Explicitly out of scope Trust accounting, tenant/owner portals, maintenance requests. Printable brochures/stock lists. Any MantisProperty-branded UI element appearing on the site. Multi-agent/staff directory features. Acceptance criteria A live listing, a sold listing, and an under-offer listing each display one single, correct status — no contradictions. Every listing has its own URL that loads directly and is crawlable (listing content present in raw page source, not only loaded via JavaScript). Carousel and listing pages visually match the rest of the site. A test enquiry submitted on a sample listing is confirmed to arrive at its intended destination. Tested on mobile and desktop. A status change made in MantisProperty (e.g. marking a test listing "Under Offer") is reflected on the site within the sync window. Reference materials MantisProperty API spec: MantisPropertyAPI_XMLSpec.pdf Live site for design/brand reference: nestseekersaustralia.com.au