ZnanyLekarz

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 API contracts indexed 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, 1 JSON-LD context, and 1 Spectral governance ruleset.

ZnanyLekarz’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 34 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

75.8/100 exemplar ▬ flat Agent 44/100 agent ready Front door AI 2/6 trace Heartbeat 93/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaidSelf serve

1 published contract 3 Agent Skills

Company Healthcare Health Tech Appointments Booking Medical Marketplace Doctors Scheduling Poland Practice Management Telehealth

What people ask ZnanyLekarz 11

The questions people put to an LLM, and the jobs they hand an agent, that ZnanyLekarz's APIs answer — each one linked to the operation that does it. Generated by API Evangelist

ZnanyLekarz Services API List the dictionary of services “Which services are in the ZnanyLekarz service dictionary?” List services offered at an address “What services does a doctor offer at a particular address, with prices?” Add a service to a doctor's address “How do I start offering a new service at a doctor's address?” Get one service offered at an address “How do I see the price and duration of one service a doctor offers at an address?”

ZnanyLekarz Bookings API List a doctor's bookings in a date range “How do I see all appointments booked with a doctor at an address between two dates?” View a single booking “How do I look up the details of one specific appointment?” Cancel a patient's booking “How do I cancel a patient's appointment on ZnanyLekarz?” Reschedule a booking to a new time or doctor “How do I reschedule an existing appointment to a different time?”

ZnanyLekarz Insurances API List available insurance providers “Which insurance companies are in the ZnanyLekarz dictionary?” List an insurer's plans “What plans does a given insurance provider offer?” List insurers accepted at an address “Which insurance providers does a doctor accept at a specific address?” Add a new insurer to an address “How do I start accepting a new insurance company at a doctor's address?”

ZnanyLekarz Calendar Breaks API List calendar breaks in a date range “Which breaks are blocked out in a doctor's calendar this month?” Block out a break in a doctor's calendar “How do I add a lunch break or day off to a doctor's calendar?” View one calendar break “How do I check the start and end of one specific calendar break?” Move a calendar break to a new time “Can I shift an existing break to a different time range instead of recreating it?”

ZnanyLekarz Addresses API List a doctor's practice addresses “Which addresses does a doctor practice at within a facility on ZnanyLekarz?” Get one of a doctor's addresses “How do I look up the details of one specific doctor address?” Change insurance support on a doctor's address “Can I change whether a doctor's address accepts insured patients?” Remove the integration mark from an address “How do I stop Docplanner treating an address as integrated with my system?”

ZnanyLekarz API Notification Callbacks API Receive pushed event notifications at my endpoint “What does the event payload look like when ZnanyLekarz pushes notifications to my endpoint?” Pull the next pending notification “How do I fetch the oldest notification I haven't pulled yet?” Pull a batch of pending notifications “Can I pull up to 100 notifications in one request?” Re-dispatch notifications that failed processing “How can I get pushed notifications that weren't processed correctly sent again?”

ZnanyLekarz Slots API List free appointment slots at an address “What free appointment times does a doctor have at an address next month?” Replace an address's slots for date ranges “How do I push my clinic's availability so it overrides existing slots?” Book a patient into a free slot “How do I book an appointment for a patient in an open slot?” Delete all slots on a given date “How do I wipe a doctor's open slots for one day?”

ZnanyLekarz Calendars API Check an address's calendar status “Is the online calendar turned on for a doctor's address?” Turn on the calendar for an address “How do I enable online booking on a doctor's address calendar?” Turn off the calendar for an address “How do I stop patients booking at an address by disabling its calendar?”

ZnanyLekarz Facilities API List my facilities “Which facilities does my ZnanyLekarz integration have access to?” Get one facility's details “How do I fetch the details of a single facility?”

ZnanyLekarz Patient Presence API Mark a patient as present at a visit “How do I record that a patient showed up for their appointment?” Mark a patient as a no-show “How do I record that a patient didn't turn up for their visit?”

ZnanyLekarz Doctors API List the doctors in a facility “Which doctors work in my facility on ZnanyLekarz?” Get one doctor's details “How do I look up a single doctor's profile in a facility?”

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 75.8/100 · exemplar

Contract Quality 13.8 / 19

Developer Ergonomics 11.3 / 15

Access Clarity 12.6 / 15

Operational Transparency 8.2 / 10

Contract Governance 2.0 / 9

Discoverability 5.0 / 8

Regulatory Posture 5.6 / 15

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 44/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/znanylekarz/"><img src="https://apis.io/badge/znanylekarz/card.svg" alt="ZnanyLekarz on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Governance scores 22.0 — up to +9.4 composite points
Contract Quality scores 73.4 — up to +6.7 composite points
Developer Ergonomics scores 75.6 — up to +4.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/znanylekarz/apis.yml: open an issue on github.com/api-evangelist/znanylekarz to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Healthcare (FHIR)	distribution	9.6 (thin)	-	-
Official SDKs on Packagist, pub.dev and Hex	distribution	9.6 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 11

Individual APIs this provider publishes, each with its own machine-readable definition.

ZnanyLekarz Addresses API

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).

ZnanyLekarz API Notification Callbacks API

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...

ZnanyLekarz Bookings API

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). ...

ZnanyLekarz Calendar Breaks API

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...

ZnanyLekarz Calendars API

Simple operations on the calendar belonging to the address

ZnanyLekarz Doctors API

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).

ZnanyLekarz Facilities API

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).

ZnanyLekarz Insurances API

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).

ZnanyLekarz Patient Presence API

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...

ZnanyLekarz Services API

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).

ZnanyLekarz Slots API

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).

Hourly Request Quota: 1 hour
Per-Minute WRITE Limit: 1 minute
Release Notifications limit: 1 hour

All 4 limits →

Billed by: subscription · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Znanylekarz Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Znanylekarz Rate Limits

4 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

ZnanyLekarz

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Znanylekarz Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Znanylekarz Notifications

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Znanylekarz Context

81 classes · 85 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

ZnanyLekarz API Rules

15 rules · 10 errors 2 warnings 3 info

SPECTRAL

OpenAPI Overlays 12

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Znanylekarz Addresses Api Phrasing Overlay

2 properties

JSON SCHEMA

Scroll for all 33

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Znanylekarz Authentication

oauth2 · 1 scheme

SECURITY

Znanylekarz Domain Security

TLSv1.3 · DMARC

SECURITY

Znanylekarz Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Znanylekarz Scopes

1 scope · clientCredentials

1 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Znanylekarz Agentic Access

44 operations · 24 acting · 2 human-in-the-loop

44 operations · 24 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

WellKnown

WellKnown

AgentSkill

AgentSkill

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Conventions

ErrorCatalog

Conformance

Lifecycle

DataModel

Scroll for all 8

Build 5

SDKs, sample code, and the tooling you integrate with

Postman

Postman

GitHubOrganization

Packages

SDKs

Examples

Access & Security 6

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 4

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 3

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Overlay

Overlay

Source (apis.yml)

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
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
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
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/znanylekarz-agentic-access.yml
- type: Spectral
  url: rules/znanylekarz-rules.yml
- type: JSONLD
  url: json-ld/znanylekarz-context.jsonld
- type: Vocabulary
  url: vocabulary/znanylekarz-vocabulary.yml
- type: Hosts
  url: hosts/znanylekarz-hosts.yml
- type: Vendors
  url: vendors/znanylekarz-vendors.yml
- 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
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
  - type: JSONSchema
    url: json-schema/znanylekarz-address-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-update-address-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-addresses-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-notification-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-pull-multiple-notifications-response-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-booking-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-bookings-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-move-booking-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-confirm-booking-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-cancel-booking-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-opinion-request-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-add-calendar-break-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-calendar-break-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-move-calendar-break-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-calendar-breaks-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-calendar-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-doctor-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-doctors-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-facility-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-facilities-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-add-address-insurance-provider-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-update-or-create-address-insurance-provider-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-address-insurance-providers-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-insurance-providers-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-insurance-plans-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-add-address-service-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-update-address-service-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-address-service-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-address-services-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-services-schema.json
- 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
  - type: JSONSchema
    url: json-schema/znanylekarz-booking-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-replace-slots-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-book-slot-request-schema.json
  - type: JSONSchema
    url: json-schema/znanylekarz-slots-schema.json
x-enrichment:
  date: '2026-10-12'
  status: enriched
  artifacts_added: 2
  pass: local-v5

ZnanyLekarz API — frequently asked questions

Does ZnanyLekarz have an API?

Yes. APIs.io lists 11 APIs from ZnanyLekarz, including ZnanyLekarz Addresses API, ZnanyLekarz API Notification Callbacks API and ZnanyLekarz Bookings API, and 8 more.

Is there an OpenAPI specification for the ZnanyLekarz API?

Yes. APIs.io indexes 11 OpenAPI specifications for ZnanyLekarz, each linked for download from this page.

How do I authenticate with the ZnanyLekarz API?

ZnanyLekarz documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Znanylekarz Authentication.

How much does the ZnanyLekarz API cost?

ZnanyLekarz publishes its prices; its Starter plan is 399 zł miesięcznie + VAT as of 2026-09-05. APIs.io lists 4 pricing plans for ZnanyLekarz, with each plan's price, limits and inclusions under Pricing on this page.

Is the ZnanyLekarz API ready for AI agents?

ZnanyLekarz has a Kin Score of 75.8 out of 100 (exemplar) and an Agent Readiness score of 44.1 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/znanylekarz"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/znanylekarz/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/znanylekarz/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.