Gratka Properties and Details Scraper
Pricing
from $3.99 / 1,000 results
Gratka Properties and Details Scraper
Gratka Properties and Details Scraper — Authorization-gated Gratka listing processing; disabled by default until prior written rights-holder permission is confirmed.
Pricing
from $3.99 / 1,000 results
Rating
0.0
(0)
Developer
Real Estate API
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
This Actor is disabled by default. Gratka's business-user rules (§§ IV.2–IV.3) prohibit copying listing content without prior rights-holder consent and prohibit commercial screen scraping. Do not set contentUseAuthorized to true unless prior written permission covers automated extraction, copying, retention, and the intended use.
When properly authorized, the Actor reads Schema.org Product/RealEstateListing JSON-LD, including nested Offer cards, and normalizes listing IDs, titles, descriptions, addresses, prices, images, rooms, area, floors, availability, and canonical URLs. Supply explicit HTTPS Gratka pages through urls and bound output with maxListings. Redirects are refused. The Actor does not sign in, contact sellers, access private listing APIs, or infer missing property values.
Local run
Use this input only when you have the required written permission. Without it, the Actor records SKIPPED_POLICY and makes no source requests.
Only records with a numeric Gratka listing ID matching the listing URL, HTTPS Gratka listing/source URLs, a non-empty title, a valid timestamp, and at least one property fact can enter the dataset. Request, parse, validation, dataset-write, summary-write, and shutdown failures stay in the SUMMARY key-value record. Clean empty results are SUCCEEDED / COMPLETED; zero-record failures are FAILED / FAILED with exit code 1; failures after saved records are SUCCEEDED / PARTIAL with exit code 0; the default gate is SUCCEEDED / SKIPPED_POLICY with zero requests and rows. Run offline checks with npm test, npm run check, and apify validate-schema.
Runtime dependency remediation — 2026-10-03
The full Actor SDK and its unused crawler, HTTP cache, FTP and proxy dependency chains were removed. The batch entrypoint now uses native fetch for the documented Apify dataset and key-value-store APIs, awaits storage acknowledgements, confines the platform credential to api.apify.com, refuses redirects, and uses the official standalone @apify/log logger. The build performs a production dependency audit and stores its exact locked application graph as RUNTIME_DEPENDENCIES. This evidence concerns the application graph, not operating-system packages. Node.js 22 or later is required.
Source permission gates, allowed hosts, advertised extraction scope, and historical storage remain unchanged. A clean dependency audit or a successful closed-gate run does not qualify source extraction. The existing written-authorization and no-retry instructions still apply.
Storage API documentation: https://docs.apify.com/api/v2/dataset-items-post and https://docs.apify.com/api/v2/key-value-store-record-put.
