ZnanyLekarz is the Polish healthcare marketplace and practice-management platform operated by Docplanner Group, connecting patients with over 146,000 listed doctors and equipping medical practices with online booking, calendar management, appointment reminders, patient reviews, e-prescriptions, video consultations and online payments. ZnanyLekarz.pl is the founding brand of the Docplanner Group and the Polish locale of the group's marketplace, which also trades as Doctoralia, MioDottore, Jameda, Doktor Takvimi and Znamylekar. Its public developer surface is the Docplanner Integrations API — an OAuth 2.0 REST API served on the www.znanylekarz.pl host that lets medical-software vendors synchronise facilities, doctors, addresses, services, insurance providers, calendars, breaks, slots and bookings, and receive push or pull event notifications when patients book, move, confirm or cancel visits.
ZnanyLekarz publishes 11 APIs on the APIs.io network, including Addresses API, API Notification Callbacks API, Bookings API, and 8 more. Tagged areas include Company, Healthcare, Health Tech, Appointments, and Booking.
The ZnanyLekarz catalog on APIs.io includes 1 event-driven AsyncAPI specification.
ZnanyLekarz’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 29 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Health regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/znanylekarz: open an issue to ask a question, or submit a pull request to add artifacts.
Submit an artifact on GitHub — free →Manage your own listing — the Influence plan, $499/mo →
More information on how we define what a Addresses is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#addresses).
More information on how we define what a API Notification Callbacks is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/callbacks/push-vs-pu...
More information on how we define what a Bookings is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#bookings). ...
More information on how we define what a Calendar Breaks is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#cale...
More information on how we define what a Doctors is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#doctors).
More information on how we define what a Facility is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#facilities).
More information on how we define what a Insurances is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#insurances).
More information on how we define what a Patient Presence is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/patient-presence.h...
More information on how we define what a Services is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#services).
More information on how we define what a Slots is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#slots).
aid: znanylekarz
name: ZnanyLekarz
description: ZnanyLekarz is the Polish healthcare marketplace and practice-management platform operated by Docplanner Group,
connecting patients with over 146,000 listed doctors and equipping medical practices with online booking, calendar management,
appointment reminders, patient reviews, e-prescriptions, video consultations and online payments. ZnanyLekarz.pl is the
founding brand of the Docplanner Group and the Polish locale of the group's marketplace, which also trades as Doctoralia,
MioDottore, Jameda, Doktor Takvimi and Znamylekar. Its public developer surface is the Docplanner Integrations API — an
OAuth 2.0 REST API served on the www.znanylekarz.pl host that lets medical-software vendors synchronise facilities, doctors,
addresses, services, insurance providers, calendars, breaks, slots and bookings, and receive push or pull event notifications
when patients book, move, confirm or cancel visits.
url: https://raw.githubusercontent.com/api-evangelist/znanylekarz/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-parent: docplanner
specificationVersion: '0.20'
created: '2026-09-05'
modified: '2026-09-05'
image: https://platform.docplanner.com/img/pl/open-graph/og-v0.png
tags:
- Company
- Healthcare
- Health Tech
- Appointments
- Booking
- Medical
- Marketplace
- Doctors
- Scheduling
- Poland
- Practice Management
- Telehealth
tags_raw:
- Company
- Healthcare
- Health Tech
- Appointments
- Booking
- Medical
- Marketplace
- Doctors
- Scheduling
- Poland
- Practice Management
- Telemedicine
apis:
- aid: znanylekarz:znanylekarz-addresses-api
name: ZnanyLekarz Addresses API
description: More information on how we define what a Addresses is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#addresses).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Addresses
properties:
- type: OpenAPI
url: openapi/znanylekarz-addresses-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-api-notification-callbacks-api
name: ZnanyLekarz API Notification Callbacks API
description: More information on how we define what a API Notification Callbacks is, its use cases and more can be found
[here](https://integrations.docplanner.com/guide/callbacks/push-vs-pull.html).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- API Notification Callbacks
properties:
- type: OpenAPI
url: openapi/znanylekarz-api-notification-callbacks-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-bookings-api
name: ZnanyLekarz Bookings API
description: 'More information on how we define what a Bookings is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#bookings).
## addBooking
In order to add a new booking use **POST** <a href="#operation/bookSlot">`bookSlot`</a> endpoint from <a href="#tag/Slots">`Slots`</a>
section.'
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Booking
tags_raw:
- Bookings
properties:
- type: OpenAPI
url: openapi/znanylekarz-bookings-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-calendar-breaks-api
name: ZnanyLekarz Calendar Breaks API
description: More information on how we define what a Calendar Breaks is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#calendar-breaks).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Calendar Breaks
properties:
- type: OpenAPI
url: openapi/znanylekarz-calendar-breaks-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-calendars-api
name: ZnanyLekarz Calendars API
description: Simple operations on the calendar belonging to the address
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Calendar
tags_raw:
- Calendars
properties:
- type: OpenAPI
url: openapi/znanylekarz-calendars-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-doctors-api
name: ZnanyLekarz Doctors API
description: More information on how we define what a Doctors is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#doctors).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Doctors
properties:
- type: OpenAPI
url: openapi/znanylekarz-doctors-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-facilities-api
name: ZnanyLekarz Facilities API
description: More information on how we define what a Facility is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#facilities).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Facilities
properties:
- type: OpenAPI
url: openapi/znanylekarz-facilities-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-insurances-api
name: ZnanyLekarz Insurances API
description: More information on how we define what a Insurances is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#insurances).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Insurances
properties:
- type: OpenAPI
url: openapi/znanylekarz-insurances-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-patient-presence-api
name: ZnanyLekarz Patient Presence API
description: More information on how we define what a Patient Presence is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/patient-presence.html).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Patient Presence
properties:
- type: OpenAPI
url: openapi/znanylekarz-patient-presence-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-services-api
name: ZnanyLekarz Services API
description: More information on how we define what a Services is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#services).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Services
properties:
- type: OpenAPI
url: openapi/znanylekarz-services-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
- aid: znanylekarz:znanylekarz-slots-api
name: ZnanyLekarz Slots API
description: More information on how we define what a Slots is, its use cases and more can be found [here](https://integrations.docplanner.com/guide/api-objects/resources.html#slots).
humanURL: https://integrations.docplanner.com/docs/
baseURL: https://www.znanylekarz.pl/api/v3/integration
tags:
- Slots
properties:
- type: OpenAPI
url: openapi/znanylekarz-slots-api-openapi.yml
- type: Postman
url: postman/znanylekarz-integrations-api.postman_collection.json
- type: Webhooks
url: asyncapi/znanylekarz-notifications.yml
- type: X-MCPServerCandidate
url: mcp/znanylekarz-mcp.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: Overlay
url: overlays/znanylekarz-integrations-api-overlay.yaml
- type: Website
url: https://www.znanylekarz.pl/
- type: DeveloperPortal
url: https://integrations.docplanner.com/
- type: Documentation
url: https://integrations.docplanner.com/guide/
- type: APIReference
url: https://integrations.docplanner.com/docs/
- type: GettingStarted
url: https://integrations.docplanner.com/guide/integration-process.html
- type: Postman
url: https://www.postman.com/run-collection/7fd8db9bb1fd14e0f0f7
- type: Support
url: https://help.docplanner.com/
- type: Blog
url: https://www.znanylekarz.pl/blog/
- type: GitHubOrganization
url: https://github.com/DocPlanner
- type: Pricing
url: https://pro.znanylekarz.pl/cennik/znanylekarz-dla-lekarzy
- type: SignUp
url: https://www.znanylekarz.pl/rejestracja-wybor
- type: TermsOfService
url: https://www.znanylekarz.pl/regulamin
- type: PrivacyPolicy
url: https://www.znanylekarz.pl/prywatnosc
- type: StatusPage
url: https://status.docplanner.com/
- type: Packages
url: packages/znanylekarz-packages.yml
- type: SDKs
url: packages/znanylekarz-packages.yml
- type: WellKnown
url: well-known/znanylekarz-well-known.yml
- type: SecurityTxt
url: well-known/znanylekarz-security.txt
- type: Security
url: security/znanylekarz-vulnerability-disclosure.yml
- type: VulnerabilityDisclosure
url: security/znanylekarz-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/znanylekarz-domain-security.yml
- type: Authentication
url: authentication/znanylekarz-authentication.yml
- type: OAuthScopes
url: scopes/znanylekarz-scopes.yml
- type: Conventions
url: conventions/znanylekarz-conventions.yml
- type: ErrorCatalog
url: errors/znanylekarz-problem-types.yml
- type: Conformance
url: conformance/znanylekarz-conformance.yml
- type: Lifecycle
url: lifecycle/znanylekarz-lifecycle.yml
- type: ChangeLog
url: changelog/znanylekarz-changelog.yml
- type: DataModel
url: data-model/znanylekarz-data-model.yml
- type: Sandbox
url: sandbox/znanylekarz-sandbox.yml
- type: Examples
url: examples/znanylekarz-examples.yml
- type: Plans
url: plans/znanylekarz-plans-pricing.yml
- type: RateLimits
url: rate-limits/znanylekarz-rate-limits.yml
- type: AgentSkill
url: skills/_index.yml
- type: LLMsTxt
url: llms/znanylekarz-llms.txt
x-enrichment:
date: '2026-09-05'
status: enriched
artifacts_added: 28
pass: local-v3
note: 'Contract discovery hit on the second pass: the Docplanner Integrations API OpenAPI 3.0.3 (v1.14.0, 32 paths, 44 operations,
82 schemas, 166 examples, 17 typed callbacks) is not served as a file anywhere — it is embedded in the __redoc_state of
the Redoc docs page at integrations.docplanner.com/docs/, and every conventional spec path on that host 404s. Ownership
confirmed from the spec itself, not from the fetch URL: its Fundamentals section maps Poland -> znanylekarz.pl, and https://www.znanylekarz.pl/api/v3/integration/facilities
returns 401 live. No MCP server, no agent card, no llms.txt, no AsyncAPI.'
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →