We extract schedules, dynamic pricing, route stopovers, and Sleepliner availability from Intercape. Delivered as clean JSON, CSV, or Parquet to S3, BigQuery, or Snowflake on your cadence.
Structured, schema-consistent data across all major object types — delivered clean, typed, and ready to query.
Complete list of extractable fields for Routes & Schedules objects from intercape.co.za. All fields typed and schema-versioned.
"route_id": "CPT-JHB-001", "origin_city": "Cape Town", "destination_city": "Johannesburg", "departure_time": "2026-08-14T14:00:00Z", "arrival_time": "2026-08-15T09:30:00Z", "bus_type": "Sleepliner", "stops_count": 4
| # | route_id | origin_city | destination_city | departure_time | arrival_time | duration_minutes |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Pricing & Availability objects from intercape.co.za. All fields typed and schema-versioned.
"route_id": "CPT-JHB-001", "departure_date": "2026-08-14", "price_zar": 850.0, "currency": "ZAR", "seats_available": 12, "ticket_class": "Sleepliner", "scraped_at": "2026-08-01T10:15:22Z"
| # | route_id | departure_date | price_zar | discount_price | currency | seats_available |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Bus Classes & Fleet objects from intercape.co.za. All fields typed and schema-versioned.
"bus_type": "Sleepliner", "class_name": "Premium", "seat_pitch_cm": 85, "wifi_available": true, "usb_charging": true, "toilet_onboard": true, "air_conditioning": true
| # | bus_type | class_name | seat_pitch_cm | recline_angle | wifi_available | usb_charging |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Stops & Boarding objects from intercape.co.za. All fields typed and schema-versioned.
"stop_id": "STP-CPT-01", "stop_name": "Cape Town Station", "city": "Cape Town", "country": "South Africa", "latitude": -33.9221, "longitude": 18.4251, "address": "Old Marine Drive, Foreshore"
| # | stop_id | stop_name | city | country | latitude | longitude |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Discounts & Policies objects from intercape.co.za. All fields typed and schema-versioned.
"policy_id": "POL-SNR-2026", "passenger_type": "Senior Citizen", "discount_pct": 15, "baggage_allowance_kg": 20, "excess_baggage_fee": 50.0, "cancellation_fee": 100.0, "change_fee": 50.0
| # | policy_id | passenger_type | discount_pct | conditions | baggage_allowance_kg | excess_baggage_fee |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Our Intercape scraper navigates complex search forms, session tokens, and route permutations across Southern Africa to extract accurate schedules and dynamic pricing.
Extract the full network across South Africa, Namibia, Botswana, Mozambique, Zimbabwe, and Malawi.
Capture fluctuating ticket prices based on demand, departure proximity, and seasonal variations.
Track remaining capacity for specific departures to gauge route popularity and load factors.
Separate Mainliner versus Sleepliner amenities, seating configurations, and pricing tiers.
Extract intermediate boarding and drop-off points for long-haul intercity journeys.
Capture precise latitude and longitude coordinates for physical bus stops and stations.
Track international route specific requirements and estimated border post transit times.
Monitor senior, student, and child fare variations alongside standard adult ticket prices.
Run daily synchronisation tasks or continuous pricing monitors with change-detection diffing.
Brief in. Clean data out.
Provide origin-destination pairs or full network mandates. We design the extraction schema together.
We configure Playwright crawlers, session management, and proxy rotation for intercape.co.za.
Schema validation, null-rate checks, price-outlier detection, and schedule verification before launch.
JSON, CSV, or Parquet pushed to your S3 bucket, BigQuery dataset, or Snowflake stage on agreed cadence.
Transport booking sites rely on heavy session state and dynamic payloads. Here is how we maintain stable data extraction.
Intercape requires valid session cookies and verification tokens to process search queries. Our infrastructure maintains persistent cookie jars and token rotation to ensure search forms submit successfully without triggering invalid request errors.
The site uses dynamic date pickers and AJAX-loaded location dropdowns. We use full Playwright browser automation to interact with these elements exactly as a human user would, capturing the resulting JSON payloads or DOM updates.
High-frequency pricing checks often trigger rate limits or geo-blocks. We route traffic through South African residential IP pools to maintain high trust scores and avoid IP bans during intensive crawl cycles.
Transport sites frequently update their booking interface layouts. We implement multi-layered fallback selectors targeting CSS classes, XPath, and internal API responses to ensure data flows even when the frontend changes.
To reduce downstream processing, we hash route pricing records. The pipeline only emits new data when ticket costs fluctuate or seat availability drops, providing a clean log of market movements.
Rival bus operators track Intercape pricing to adjust their own dynamic fares and remain competitive on shared routes.
OTA platforms integrate schedule and pricing data into multi-modal transport engines for comprehensive journey planning.
Transport analysts study frequency and capacity across corridors to identify underserved markets and optimise fleet deployment.
Tour operators sync intercity bus availability with local accommodation packages to create unified travel itineraries.
Analysts track cross-border passenger transport volume as a proxy for regional economic activity and migration patterns.
Urban planners utilise historical schedule data to model regional mobility networks and assess public transport accessibility.
"Intercity bus networks form the circulatory system of Southern Africa. Querying that schedule data programmatically requires navigating complex session states."
Most teams underestimate the investment required: reliable transport scraping requires managing search session tokens, rendering dynamic date pickers, and handling regional IP blocks. DataFlirt absorbs that complexity so your engineers can focus on the analysis, not the infrastructure.
Everything supported by our intercape.co.za scraper — rendered SPA elements, auth walls, rate-limit evasion and beyond.
Open-source tooling on proven cloud infra — no vendor lock-in, full observability.
Scrapy handles crawl orchestration and deduplication. Playwright handles JavaScript rendering, date picker interaction, and token management.
We maintain pools of residential ISP proxies across Southern Africa. Rotation happens per-request to avoid regional rate limits.
Pipelines run on AWS Lambda and ECS. Airflow handles scheduling, dependency management, and SLA alerting.
Data delivered to where your team already works — no new tooling required.
About intercape.co.za scraping, legality, and pipeline operations.
Ask us directly →Scraping publicly available schedule and pricing information is generally permissible. DataFlirt targets only public, non-authenticated route data. We do not extract personal user data or circumvent authentication walls.
We use Playwright to automate browser interactions, selecting origins, destinations, and dates exactly as a human would, ensuring the correct session tokens are generated for the search request.
Yes. We cover the entire Intercape network, including routes spanning South Africa, Namibia, Botswana, Mozambique, Zimbabwe, and Malawi.
Pipelines can be configured to run daily for general schedule monitoring, or at hourly intervals for specific high-priority routes to track dynamic pricing changes.
Yes. The extraction schema separates bus classes, capturing the distinct pricing, amenities, and availability for both Mainliner and Sleepliner services.
Our minimum engagement typically starts with a defined list of origin-destination pairs monitored on a daily cadence. Contact us with your specific route requirements for a quote.
20-minute scoping call. Pilot dataset within the week. Production within two. Whether you need a one-off route network export or a continuous price-monitoring feed across Southern Africa, we build and operate the pipeline. Tell us what you need.
