We extract clinic directories, practitioner profiles, symptom guides, and dynamic booking availability from Kry. Delivered as clean JSON, CSV, or Parquet to your warehouse.
Structured, schema-consistent data across all major object types — delivered clean, typed, and ready to query.
Complete list of extractable fields for Clinics & Locations objects from kry.se. All fields typed and schema-versioned.
"clinic_id": "KRY-CL-084", "name": "Kry Vardcentral Gallerian", "region": "Stockholm", "postal_code": "111 52", "latitude": 59.3312, "longitude": 18.0668, "drop_in_available": true
| # | clinic_id | name | region | address | postal_code | latitude |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Practitioners objects from kry.se. All fields typed and schema-versioned.
"practitioner_id": "PR-99214", "full_name": "Dr. Anna Lindberg", "title": "General Practitioner", "specialty": "Family Medicine", "languages_spoken": "['Swedish', 'English']", "available_for_video": true, "primary_clinic_id": "KRY-CL-084"
| # | practitioner_id | full_name | title | specialty | languages_spoken | gender |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Appointment Slots objects from kry.se. All fields typed and schema-versioned.
"slot_id": "SL-20261014-0830", "clinic_id": "KRY-CL-084", "appointment_type": "Physical Consultation", "start_time": "2026-10-14T08:30:00Z", "price_sek": 250, "is_subsidised": true, "scraped_at": "2026-10-12T09:14:00Z"
| # | slot_id | clinic_id | practitioner_id | appointment_type | start_time | end_time |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Treatments & Services objects from kry.se. All fields typed and schema-versioned.
"treatment_id": "TR-ALLERGY-01", "category": "Allergy", "title": "Pollen Allergy Assessment", "base_price_sek": 250, "estimated_duration_mins": 15, "requires_referral": false, "age_restriction": "16+"
| # | treatment_id | category | sub_category | title | description | required_preparation |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Complete list of extractable fields for Symptom Guides objects from kry.se. All fields typed and schema-versioned.
"article_id": "ART-992", "slug": "halsfluss", "title": "Halsfluss (Tonsillit)", "medical_reviewer": "Dr. Johan Svensson", "last_updated": "2025-11-02", "icd_10_codes": "['J03.9']", "tags": "['Infection', 'Throat']"
| # | article_id | slug | title | medical_reviewer | publish_date | last_updated |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 |
Our Kry scraper handles the complexities of telehealth platforms: dynamic booking APIs, regional geo-blocking, and nested JSON payloads.
Extract physical clinic addresses, coordinates, opening hours, and contact details across all operating regions.
Capture practitioner names, specialties, spoken languages, and primary clinic affiliations.
Scrape calendar APIs to extract available slot times for physical and video consultations.
Extract base prices, subsidised rates, and referral requirements for all listed medical services.
Scrape medically reviewed articles, symptom guides, and associated ICD-10 code mappings.
Standardise location coordinates and regional identifiers for immediate use in BI tools.
Map data across Kry.se (Sweden), Kry.no (Norway), and Livi.co.uk (UK) using a unified schema.
Only emit updates for changed practitioner rosters or new clinic openings to reduce processing overhead.
Bypass frontend rendering to interact directly with backend slot and availability APIs.
Brief in. Clean data out.
Provide target regions, clinic IDs, or specialty categories. We design the extraction schema together.
We configure Scrapy crawlers, Nordic proxy rotation, and API reverse engineering for Kry's endpoints.
Schema validation, null-rate checks, and location coordinate verification before full launch.
JSON, CSV, or Parquet pushed to your S3 bucket or Snowflake stage on agreed cadence.
Modern telehealth platforms heavily protect their APIs and content. Here is how we maintain reliable extraction.
Appointment slots on Kry use complex stateful APIs that require specific token handshakes. We reverse engineer these flows to extract slot availability directly from the backend, bypassing slow frontend rendering.
Kry aggressively blocks non-Nordic IP addresses. Our infrastructure routes requests through ISP-grade residential proxies located in Sweden and Norway to maintain access and prevent rate limiting.
Much of Kry's static data is embedded within Next.js build payloads. We parse these JSON objects directly from the DOM, ensuring we capture all metadata without relying on fragile CSS selectors.
Healthcare taxonomies and category slugs change frequently. We employ fuzzy matching and structured fallback chains to ensure treatment categories map correctly even when the frontend layout updates.
We normalise Swedish strings, address formats, and timestamps into standard ISO formats, ensuring the data is ready for analysis immediately upon delivery.
Researchers analyse wait times, slot availability, and clinic distribution to measure regional healthcare access.
Private clinic operators track Kry's pricing matrices, service offerings, and clinic expansion strategies.
Analysts map specialist density across regions to identify underserved demographics and recruitment opportunities.
Healthcare strategists track the ratio of physical to video consultations across different medical specialties.
Digital health publishers analyse symptom search density and article coverage to guide their own medical content production.
Public health officials predict clinic demand based on available slot velocity and symptom guide traffic.
"Mapping digital healthcare infrastructure requires structured visibility into clinic availability and practitioner distribution across Sweden. We normalise the data so you can build the models."
Extracting data from modern telehealth platforms involves navigating strict rate limits, regional geo-blocking, and complex stateful APIs for booking calendars. DataFlirt manages the proxy rotation, endpoint reverse engineering, and schema validation, delivering clean datasets directly to your analysts.
Everything supported by our kry.se scraper — rendered SPA elements, auth walls, rate-limit evasion and beyond.
Open-source tooling on proven cloud infra — no vendor lock-in, full observability.
We trace and replicate the exact token handshakes required by Kry's backend to extract data efficiently without loading heavy frontend assets.
We maintain pools of residential ISP proxies specifically in Sweden and Norway to bypass strict regional IP blocks and rate limits.
Pipelines run on AWS Lambda and ECS. Airflow handles scheduling, dependency management, and SLA alerting. All state is stored in managed Postgres.
Data delivered to where your team already works — no new tooling required.
About kry.se scraping, legality, and pipeline operations.
Ask us directly →Scraping publicly available directory information, clinic locations, and anonymised slot availability is generally permissible. DataFlirt strictly targets public data. We do not extract patient records, PII, or circumvent authentication walls.
We reverse engineer the Next.js data props and backend API endpoints. This allows us to query slot availability directly using the correct headers and tokens, avoiding the overhead of full browser rendering.
Yes. Kry operates as Livi in the UK and France. We map data from both brands into a single, unified schema for cross-regional analysis.
Slot availability changes rapidly. We can configure pipelines to poll specific high-priority clinics at hourly intervals, while scanning the broader directory daily.
Yes, we extract healthcare provider registry numbers and credentials wherever they are publicly listed on the practitioner profile pages.
Kry restricts access from non-Nordic IP ranges. We route all requests through high-quality residential proxies located in Sweden and Norway to simulate genuine local traffic.
Yes. We provide a sample run covering up to 5 clinics or 50 practitioner profiles to validate schema fit and data quality before formal engagement.
20-minute scoping call. Pilot dataset within the week. Production within two. Whether you need a one-off clinic directory map or a continuous feed of appointment slot availability, we scope, build, and operate the pipeline. Tell us what you need.
