Catalog / Retail, marketplaces & classifieds
RETAIL, MARKETPLACES & CLASSIFIEDS · BRAZIL
OLX Brasil Classifieds & Real Estate
Collect OLX Brazil general classifieds and real estate listings, with pagination, duplicate suppression, optional detail pages and a maximum result count.
About this data
Collect OLX Brazil general classifieds and real estate listings, with pagination, duplicate suppression, optional detail pages and a maximum result count.
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/olx/listings
Records include listing IDs, titles, source URLs, displayed BRL prices, categories, state/city/neighborhood, posting times, professional-seller flags and images where published.
Read one results page for a keyword and Brazilian state, up to 20 listings.
No later pages, listing details, seller profiles, names or phone numbers are fetched.
Input
Send a JSON body to POST https://api.ssh.autos/v1/br/olx/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
keyword | string | optional | up to 150 characters; default "bicicleta" |
state | string | optional | pattern ^(AC|AL|AP|AM|BA|CE|DF|ES|GO|MA|MT|MS|MG|PA|PB|PR|PE|PI|RJ|RN|RS|RO|RR|SC|SP|SE|TO)$; default "SP" |
maxResults | integer | optional | 1–20; default 5 |
Returned fields
The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 23 fields; a field the source does not publish comes back null.
23 fields per record
| Field | Type | Notes |
|---|---|---|
listingId | string | — |
url | string | — |
price | number | — |
currency | string | — |
category | string | — |
state | string | — |
city | string | — |
neighborhood | string | — |
postalCode | string | — |
postedDate | string | — |
professionalSeller | boolean | — |
images | array of strings | — |
propertyType | string | — |
businessType | string | — |
bedrooms | number | — |
bathrooms | number | — |
usableAreaM2 | number | — |
condoFee | number | — |
iptu | number | — |
parkingSpaces | number | — |
amenities | array of strings | — |
sellerName | string | Public source value, null when absent. |
sellerPhone | string | Public source value, null when absent. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/br/olx/listings -m POST -b '{"keyword": "bicicleta", "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
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
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: OLX Brasil Classifieds & Real Estate Scraper. 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.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - 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.
- 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