Replay a Redfin Search URL as JSON
View all Redfin Property Data endpoints →Convert a hand-built Redfin search URL into structured JSON. Paste the full link a user crafted on the website (for example a city apartments-for-rent page with on-site filters and pagination baked into the path) and receive the matching result rows instead of scraping the rendered page. Ideal for mirroring saved searches: whatever the URL encodes (area, listing type, page number) is replayed server-side and returned as listing data.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/redfin/property-search-by-url API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/redfin/property-search-by-url?key=<API_KEY>&url=https%3A%2F%2Fwww.redfin.com%2Fcity%2F30749%2FNY%2FNew-York%2Fapartments-for-rent%2Fpage-1'
Query Result
Use Cases
- Replay a user's hand-tuned saved-search URL and receive the same results as structured JSON.
- Let users paste any Redfin search link into your app and instantly mirror the result set.
- Bulk-ingest a curated library of search URLs covering target markets for a nightly sync job.
- Migrate a bookmark-based research workflow into a database without rebuilding filters.
Frequently asked questions
How do I avoid IP bans when scraping Redfin? Is there an alternative?
Running your own crawler means maintaining proxy pools and anti-blocking logic — costly and unstable. This endpoint returns the structured JSON behind a search results page directly: paste the link and skip page scraping altogether.
Is pagination in the link preserved?
Yes. /page-N path segments are replayed faithfully, so batch jobs can walk a saved search page by page.
What links are accepted?
Full search-results URLs (with filters and /page-N path segments) can be replayed; for a single-property detail link, use the detail-by-URL endpoint instead.