Dealground

Last reviewed: July 2026

Overview

Integuru's Dealground integration provides production-ready HTTP API access to Dealground, the commercial real estate deal sourcing platform at app.dealground.com, covering 3 actions: search_listings, get_listing_documents, and list_brochures. Full API documentation is available for all three actions.

No public API. Dealground exposes no developer API. Investment teams that need to query deal flow programmatically have had to log in manually or build fragile browser scripts tied to specific page layouts, both of which break whenever the UI changes.

The search_listings action accepts over 30 filter parameters spanning property type, subtype, location (state, city, or geographic bounding box), NOI range, asking price range, building and land square footage, year built, tenancy type, lease type, tenant name, and three paired date ranges for market date, last sold date, and debt maturity date. Results paginate at up to 50 listings per page.

Investment analysts, deal sourcing tools, and proptech engineering teams use this integration to run programmatic screens against the Dealground catalog, retrieve listing documents by spatial entity ID, and pull brochures filtered by property type and geography. Browse the full integrations catalogue for other Finance & Investing and real estate platform integrations.

---

Use Cases

Integuru's Dealground integration supports the full deal sourcing workflow: screening the listing catalog with rich filters, pulling attached documents for a specific property, and browsing available brochures by geography and asset type.

• Programmatic deal screening: Call search_listings with noi_min, noi_max, type, state, and listed_price_max to run investment criteria screens against the Dealground catalog. Combine subtypes (e.g. ['Warehouse', 'Medical Office']) with tenant_name to narrow to specific asset profiles.
• Listing document retrieval: Call get_listing_documents with the spatial_entity_id returned from a search_listings result to pull all documents attached to a specific property (offering memoranda, financials, rent rolls, etc.).
• Brochure discovery: Use list_brochures to browse available marketing brochures filtered by city, state, property type, subtype, and tenant. Pagination works identically to search_listings, with up to 50 results per page.
• Geographic area search: Pass a bounding_box object to search_listings to restrict results to a specific map region, replacing manual city or state arrays when your target area does not align with state or city boundaries.
• Debt maturity pipeline: Use the debt_maturity_date_start and debt_maturity_date_end pair on search_listings to identify properties with upcoming debt maturities, a common signal for deal flow origination.

---

Setup Notes

Integuru's Dealground integration authenticates against https://app.dealground.com/. Integuru handles the login session automatically; you configure credentials once during setup and the integration manages re-authentication from that point forward.

Pagination: Both search_listings and list_brochures use page-based pagination. Pass page (starts at 1) and page_size (max 50) to scroll through result sets. Omitting page_size returns the platform default.

Date range pairs: Three date filters on search_listings require paired start and end values. Each pair must be supplied together or omitted entirely:

• date_on_market_start and date_on_market_end
• last_sold_date_start and last_sold_date_end
• debt_maturity_date_start and debt_maturity_date_end

All dates use YYYY-MM-DD format. When using the last_sold_date pair, set sold_within_period: true to restrict results to properties sold inside the date range rather than on or before it.

Bounding box: The bounding_box parameter on search_listings takes an object with east, west, north, and south keys as decimal degree coordinates. Use it when your target area does not map cleanly to state or city arrays.

Array vs. single-value params on list_brochures: Several list_brochures params (city, type, state, subtype, tenant_name) accept either a single string or an array of strings. Pass a single string to target one value; pass an array to match multiple.