Skip to content
HomeAPI documentation

Maria Torres Homes · Developer resources

API documentation

A practical reference for connecting property search, listing details and photography to Maria’s South Florida website.

Websitemariatorreshomes.comSite identifierm.torres.flMarketSouth Florida · BEACH

01 / Access

The property gateway.

The website uses a site-scoped, read-only gateway. Its server supplies the private IDX credential; browser requests do not need an API key, account token or cookies.

Property gateway base URL
https://tophamtechbe.com/api/treas/idx/v1/website/m.torres.fl

Browser requests must come from a registered origin. Maria’s production origins are https://mariatorreshomes.com and https://www.mariatorreshomes.com; staging uses https://main.d1z44nj1jdznyw.amplifyapp.com. A new website origin must be registered before browser access will work. Server requests can omit the Origin header.

Access has a defined scope.

This gateway accepts property GET requests only. It does not grant access to private accounts, CRM records, contact submission or administration. MLS display, reuse and redistribution remain subject to the applicable approvals and terms.

02 / Quick start

Begin with a small search.

This request retrieves up to six Fort Lauderdale results from Maria’s authorized BEACH feed. Availability and results change; use the live response.

Search with curl
curl --get 'https://tophamtechbe.com/api/treas/idx/v1/website/m.torres.fl/summary/page' \
  --data-urlencode 'state=FL' \
  --data-urlencode 'city=Fort Lauderdale' \
  --data-urlencode 'originatingSystemName=BEACH' \
  --data-urlencode 'pageSize=6' \
  --data-urlencode 'firstPhoto=true' \
  --header 'Accept: application/json'
Search from a registered website
const response = await fetch(
  'https://tophamtechbe.com/api/treas/idx/v1/website/m.torres.fl/summary/page?state=FL&city=Fort%20Lauderdale&originatingSystemName=BEACH&pageSize=6&firstPhoto=true',
  { credentials: 'omit', headers: { Accept: 'application/json' } }
);
if (!response.ok) throw new Error(`Property search failed: ${response.status}`);
const { properties, pagination } = await response.json();

04 / Property details

Follow the listing key.

Take listing_key from a search result and pass it as the camelCase query parameter listingKey. Do not substitute an MLS display number or guess a listing identifier.

Retrieve listing details
const url = new URL('https://tophamtechbe.com/api/treas/idx/v1/website/m.torres.fl/data');
url.searchParams.set('listingKey', listing.listing_key);
const response = await fetch(url, { credentials: 'omit' });

The response contains a properties array and total_count. Use the returned property fields and current status; account for missing values. Link to a website listing using /listing/ followed by the encoded listing key.

05 / Photography

Use the listing’s own media.

Listing media endpoint
https://tophamtechbe.com/api/treas/idx/v1/website/m.torres.fl/media/LISTING_KEY

Replace LISTING_KEY with the encoded key from search. Media responses contain a media array and total_count. Entries may include media_url, s3_link and order_hint. Handle empty media, use descriptive image alternatives and preserve required attribution. MLS photography is separate from illustrative lifestyle imagery on editorial pages.

06 / Contact & showings

Keep the customer in control.

For a personal inquiry, use Maria’s contact page. To request a showing, open the property in property search and choose its showing action. Those flows collect the customer’s details and the required consent.

Separately authorized contact integrations

The shared service provides POST /api/treas/idx/v1/chatleads for approved integrations. This is outside the property gateway and requires a separately authorized credential and any required Turnstile verification. A property-read credential does not establish permission to submit leads.

Authorized contact request fields
Query parameterMeaning
siteIdm.torres.fl
name, email, phoneNumberCustomer details supplied for the inquiry.
serviceReqThe customer’s explicit request.
listingKeyOptional listing context from a search result.

Submit these as URL-encoded query parameters rather than a JSON body. Authorized callers use the X-API-Key header and, when required, X-Turnstile-Token. Keep private credentials on the server. Submit only after the customer asks to send an inquiry; an unclear timeout is not permission to resend a lead or create a showing.

07 / Errors & limits

Handle the next step clearly.

HTTP response guidance
StatusRecommended handling
400Correct invalid filters, identifiers or pagination parameters.
401 / 403Check access, the registered origin and integration permissions.
404The listing, route or site registration is unavailable.
405The property gateway permits GET requests only.
429Respect Retry-After and reduce request frequency.
502 / 503 / 504Show a temporary-unavailability message; retry property reads with backoff.

Limits are configured per site and caller. Respect Retry-After, cancel obsolete searches and debounce map movement. Preserve a useful empty or error state instead of presenting old results as current inventory.

08 / Support

Build with the right context.

For technical integration support, contact support@agentwinds.com and include site ID m.torres.fl, the endpoint, status code and approximate request time. Exclude credentials and customer information.

For real estate questions, contact Maria Torres. Public business identity is available in llms.txt. Review the Privacy Policy and Terms of Service before integrating.

Reference checked October 8, 2026. Examples describe request structure and do not promise listing availability.

Your next chapter

Let’s make your next move
a considered one.

Start a conversation