How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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

ZnanyLekarz Slots API is one of 11 APIs that ZnanyLekarz publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Slots. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 3 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.14.0.

Requests are made against a single base URL, https://www.{domain}/api/v3/integration.

4 operations 3 paths 14 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.14.0
Base URL
https://www.znanylekarz.pl/api/v3/integration
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

ZnanyLekarz Slots API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • oauth2 — The API utilizes the industry-standard [OAuth 2.0](https://tools.ietf.org/html/rfc6749) protocol. All requests to our API must be authenticated and must includ…

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Slots 4

More information on how we define what a Slots is, its use cases and more can be found here.

GET
/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slots
Get slots
getSlots 6 params → 200400403404
PUT
/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slots
Replace slots
replaceSlots 3 params body → 201400403404422429
POST
/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slots/{start}/book
Book slot
bookSlot 4 params body → 200400403404422
DELETE
/facilities/{facility_id}/doctors/{doctor_id}/addresses/{address_id}/slots/{date}
Delete slots
deleteSlots 4 params → 204403404

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Booking (18 properties), AddressService (11 properties), BookingPatient (9 properties), Patient (9 properties). Each schema is shown below with its type and property counts.

AddressServices
object
1 property
Slot
object
2 properties
Patient
object
9 properties 2 required
AddressService
object
11 properties
Insurance
object
4 properties
Error
object
2 properties
Slots
object
1 property
BookingPatient
object
9 properties
ReplaceSlotsRequest
object
1 property 1 required
Booking
object
18 properties
SlotsScopes
string
BookingMoving
object
2 properties
AllowedPatientsData
object
2 properties
BookSlotRequest
object
9 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

znanylekarz-slots-api-openapi.yml Raw ↑

Other APIs ZnanyLekarz publishes across the network.

ZnanyLekarz Addresses API
ZnanyLekarz API Notification Callbacks API
ZnanyLekarz Bookings API
ZnanyLekarz Calendar Breaks API
ZnanyLekarz Calendars API
ZnanyLekarz Doctors API
ZnanyLekarz Facilities API
ZnanyLekarz Insurances API
ZnanyLekarz Patient Presence API
ZnanyLekarz Services API
Where this information came from

This is an independent, third-party profile of ZnanyLekarz Slots API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.