ssh.autos

Catalog / Real estate

REAL ESTATE · BRAZIL

VivaReal & ZAP Imóveis: Brazil Property Listings

Collect public Brazilian property listings from VivaReal and ZAP Imóveis as structured records with BRL prices, areas, room counts, location, amenities, images and source links.

PER CALL · X402 / MPP From $0.02 per call 1 endpoint at api.ssh.autos. Pay in USDC, no account. See the endpoint
APIFY STORE Public actor Run it with your Apify account: bulk runs, schedules and exports. Open on Apify

About this data

Collect public Brazilian property listings from VivaReal and ZAP Imóveis as structured records with BRL prices, areas, room counts, location, amenities, images and source links.

From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.

Buy per call over x402

One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.

POST /v1/br/vivareal-zap/listings

Fetch one results page with up to 20 Brazilian property listings from one portal per call.

PRICE$0.02 per call, in USDC
RESULTUp to 20 per call
PAYMENTx402 or MPP · no account

Filter by city, state, sale or rent, property type and price.

Records include titles, BRL prices, areas, bedrooms, bathrooms, parking, neighborhood, agency names, images and source URLs; fees and taxes appear when published.

No detail or contact endpoints are requested.

Input

Send a JSON body to POST https://api.ssh.autos/v1/br/vivareal-zap/listings.

FieldTypeRequiredNotes
portalstringoptionalone of vivareal, zap; default "vivareal"
citystringoptional1–100 characters; default "São Paulo"
statestringoptional2–40 characters; default "SP"
businessTypestringoptionalone of sale, rent; default "sale"
propertyTypestringoptionalone of all, apartment, house, condominium, land, commercial; default "all"
minPricenumberoptionalat least 0
maxPricenumberoptionalat least 0
maxResultsintegeroptional1–20; default 10

Returned fields

The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 31 fields; a field the source does not publish comes back null.

31 fields per record
FieldTypeNotes
listingIdstring—
portalstring—
businessTypestring—
propertyTypestring—
pricenumber—
currencystring—
condoFeenumber—
iptunumber—
iptuPeriodstring—
usableAreaM2number—
totalAreaM2number—
bedroomsnumber—
bathroomsnumber—
suitesnumber—
parkingSpacesnumber—
streetstring—
neighborhoodstring—
citystring—
statestring—
latitudenumber—
longitudenumber—
amenitiesarray of strings—
imageUrlsarray of strings—
advertiserPhonesarray or string or objectPublished advertiser phones in source format, filled only when the source page carries them (searchUrl pages); null on the default search or when unavailable.
advertiserEmailsarray or string or objectPublished advertiser emails in source format, filled only when the source page carries them (searchUrl pages); null on the default search or when unavailable.
advertiserContactobject or array or stringPublished advertiser contact information, filled only when the source page carries it (searchUrl pages); null on the default search or when unavailable.
agencyNamestringPublished advertiser name, including individual advertisers, regardless of license or contract type.
createdAtstring—
updatedAtstring—
urlstring—
observedAtstring—

Example call

TERMINAL · $0.02 PER RUN
npx agentcash@latest fetch https://api.ssh.autos/v1/br/vivareal-zap/listings -m POST -b '{"city": "São Paulo", "state": "SP", "maxResults": 5}'

The example values come from the API spec or the actor’s own sample input. Running it is a paid call.

What is and isn’t charged

Free

  • Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
  • Invalid input and source failures are not charged.

Prefer a subscription? Run it on Apify

This data source is a public actor on the Apify Store: VivaReal & ZAP Imóveis Scraper: Brazil Property Listings. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.

Open on Apify

How x402 payment works

  1. Your client sends the request. The API answers 402 Payment Required with the price and where to pay.
  2. The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
  3. The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.

The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.

Machine-readable: openapi.json · llms.txt

Some links to Apify are affiliate links. We may earn a commission if you sign up and become a paying customer.