Oladoc Doctors Scraper ๐Ÿฉบ avatar

Oladoc Doctors Scraper ๐Ÿฉบ

Pricing

Pay per usage

Go to Apify Store
Oladoc Doctors Scraper ๐Ÿฉบ

Oladoc Doctors Scraper ๐Ÿฉบ

Efficiently extract doctor profiles, specialties, and consultation fees from Oladoc. This lightweight scraper is built for speed and ease of use. For optimal performance and to ensure uninterrupted data collection, the use of residential proxies is strongly recommended.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Shahid Irfan

Shahid Irfan

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

0

Monthly active users

13 days ago

Last modified

Share

Oladoc Doctors Scraper

Extract comprehensive doctor listings from Oladoc with rich hospital, availability, fee, review, and service data. Collect clean healthcare data for research, directory building, competitive analysis, and appointment marketplace workflows.


Features

  • Rich doctor records โ€” Collect doctor profiles with specialties, qualifications, ratings, review counts, fees, PMDC verification, and profile summaries.
  • Hospital and booking coverage โ€” Capture clinics, video consultation locations, bookable hospitals, fees, and availability details.
  • Duplicate-free output โ€” Save only unique doctor records and remove empty values from nested data.
  • Flexible entry points โ€” Start from specialty and city inputs or use a direct Oladoc listing URL.
  • Pagination support โ€” Continue through listing pages until your target result count is reached.

Use Cases

Healthcare Market Research

Analyze doctor density, specialties, consultation fees, and availability across cities and localities. Build datasets for reports, dashboards, and regional comparisons.

Medical Directories

Create searchable doctor and clinic directories with profile images, specialties, hospitals, service lists, and booking metadata.

Appointment Intelligence

Track which doctors are bookable, where they practice, when they are available, and which consultation modes they support.

Competitive Analysis

Compare ratings, review volume, service breadth, and pricing patterns across doctors, clinics, and specialties.

Data Enrichment

Enrich healthcare CRM systems, lead lists, or internal datasets with verified profile and location details.


Input Parameters

ParameterTypeRequiredDefaultDescription
startUrlStringNoโ€”Direct Oladoc listing URL. When provided, it takes precedence over specialty, city, and country.
specialtyStringNoโ€”Specialty slug to scrape, such as dermatologist or cardiologist.
cityStringNoโ€”City slug to scrape, such as lahore or karachi.
countryStringNopakistanCountry slug used when building the listing URL from inputs.
collectDetailsBooleanNotrueInclude richer nested hospital and service data in the output.
results_wantedIntegerNo20Maximum number of doctor records to collect.
max_pagesIntegerNo10Maximum number of listing pages to process.
proxyConfigurationObjectNoApify ProxyProxy settings for reliable collection at scale.

Output Data

Each dataset item contains clean doctor data with empty values removed.

FieldTypeDescription
doctor_idStringUnique doctor identifier on Oladoc.
nameStringDoctor display name.
urlStringDoctor profile URL.
specialtyStringMain specialization string from the listing.
qualificationsStringDegrees and educational credentials.
experienceStringHuman-readable experience value.
experience_yearsIntegerNumeric years of experience.
ratingNumberAverage rating score.
reviews_countIntegerTotal number of reviews.
consultation_feeStringConsultation fee or fee range.
wait_timeStringAverage wait time shown on the listing.
availabilityStringCurrent availability text when present.
cityStringDoctor city.
localityStringPrimary locality value.
phoneStringContact number used for appointments.
descriptionStringClean profile summary text.
pmdc_verifiedBooleanWhether the doctor is marked as PMDC verified.
servicesObjectService list and service count when available.
hospitalsArrayHospital and clinic entries returned for the doctor.
bookable_hospitalsArrayBookable hospital entries for the doctor.
vc_hospitalsArrayVideo consultation locations and details.
subscribed_hospitalsArraySubscribed practice locations returned by the listing.
all_hospitalsArrayDeduplicated combined hospital list.

Additional fields from the source listing may also be included when available, including booking flags, image URLs, fee metadata, review percentages, service metadata, and specialization slugs.


Usage Examples

{
"specialty": "dermatologist",
"city": "lahore",
"results_wanted": 20
}

Direct Listing URL

{
"startUrl": "https://oladoc.com/pakistan/lahore/dermatologist",
"results_wanted": 30,
"max_pages": 5
}

Rich Hospital Data

{
"specialty": "cardiologist",
"city": "karachi",
"collectDetails": true,
"results_wanted": 50,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"]
}
}

Sample Output

{
"doctor_id": "1601408",
"name": "Dr. Alina Abbas",
"url": "https://oladoc.com/pakistan/lahore/dr/dermatologist/alina-abbas/1601408",
"specialty": "Dermatologist, Cosmetologist",
"qualifications": "M.B.B.S., F.C.P.S.",
"experience": "8 Years",
"experience_years": 8,
"rating": 4.9,
"reviews_count": 1238,
"consultation_fee": "1500 - 2500",
"wait_time": "15 - 30 Min",
"availability": "today",
"city": "Lahore",
"locality": "Johar Town",
"phone": "04238900939",
"description": "Dr. Alina Abbas is one of the best Dermatologist in Lahore.",
"pmdc_verified": true,
"services": {
"count": 39,
"items": [
"Acne Treatment",
"Alopecia",
"Antihistamine Treatment",
"Boil",
"Carbon Facial"
],
"user_id": "1601408"
},
"all_hospitals": [
{
"doctor_id": "1601408",
"hospital_id": "4681",
"name": "Online Video Consultation",
"locality": "Online",
"city": "Video Consultation",
"fee": 1500,
"when_available": "Tue, Apr 14",
"video_consultation": true,
"book": true
},
{
"doctor_id": "1601408",
"hospital_id": "117",
"name": "Ihsan Mumtaz Hospital",
"locality": "Johar Town",
"city": "Lahore",
"fee": 2500,
"when_available": "today",
"video_consultation": false,
"book": true
}
]
}

Tips for Best Results

Start With Working Listings

  • Use valid specialty and city slugs.
  • If you already have a listing page open, pass it via startUrl.

Keep Test Runs Small

  • Start with results_wanted: 20 for quick validation.
  • Increase result count once you confirm the output shape you need.

Use Proxies For Larger Runs

  • Residential proxies improve reliability on longer runs.
  • Keep pagination limits realistic to reduce retries and runtime.

Choose Detail Level Deliberately

  • Leave collectDetails enabled when you need hospital arrays and service details.
  • Disable it when you want lighter records and faster downstream processing.

Integrations

  • Google Sheets โ€” Export doctor and clinic data for reporting.
  • Airtable โ€” Build searchable healthcare directories.
  • Make โ€” Trigger downstream workflows after each run.
  • Zapier โ€” Sync doctor records with business tools.
  • Webhooks โ€” Send fresh data into internal systems.

Export Formats

  • JSON โ€” Best for APIs and application workflows.
  • CSV โ€” Useful for spreadsheets and flat-file analysis.
  • Excel โ€” Good for business teams and reports.
  • XML โ€” Helpful for legacy system integrations.

Frequently Asked Questions

Can I scrape multiple pages?

Yes. The actor paginates through listing pages until it reaches your requested result count or the configured page limit.

What happens when startUrl is provided?

The actor uses that listing as the source and ignores specialty, city, and country for URL construction.

Does the dataset include hospital information?

Yes. When collectDetails is enabled, the output includes hospital, bookable hospital, video consultation, and merged hospital arrays when available.

Are empty fields kept in the output?

No. The actor removes null, empty, and duplicate values from records before saving them.

Can I collect doctors from other specialties?

Yes. Use any valid Oladoc specialty listing supported by the website.


Support

For issues or feature requests, use the Apify Console discussion and support channels.

Resources


This actor is intended for legitimate data collection and analysis workflows. Users are responsible for ensuring their use complies with applicable laws, platform terms, and internal data governance requirements.