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

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

Tagged areas include API Notification Callbacks. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 4 paths, and defines 37 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 4 paths 37 schemas 2 GET2 POST

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 API Notification Callbacks 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 4 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

API Notification Callbacks 4

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

POST
/{client-endpoint-url}
Push notifications
Push Notifications → 200
GET
/notifications
Pull notification
Pull Notification → 200404
GET
/notifications/multiple
Pull multiple notification
Pull Multiple Notification 1 param → 200404
POST
/notifications/release
Release notifications
Release Notifications → 204403429

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are BookingNotification (16 properties), AddressService (11 properties), Address (10 properties), VisitBookingRequestNotification (10 properties). Each schema is shown below with its type and property counts.

AddressAssignedNotification
object
3 properties
Patient
object
9 properties 2 required
Specialization
object
2 properties
PullMultipleNotificationsResponse
object
2 properties
Doctor
object
6 properties
LicenseNumbers
object
1 property
AddressService
object
11 properties
AddressCommercialTypeChangedNotification
object
3 properties
Notification
object
3 properties
Error
object
2 properties
BookingMovedNotification
object
3 properties
SlotBookedNotification
object
3 properties
Doctors
object
1 property
AddressServiceChangedNotification
object
3 properties
BookingConfirmedNotification
object
3 properties
BookingCanceledNotification
object
3 properties
PresenceMarkedNotification
object
3 properties
BookingNotification
object
16 properties
Facility
object
3 properties
AllowedPatientsData
object
2 properties
AddressServiceDeletedNotification
object
3 properties
BreakCreatedNotification
object
3 properties
Specializations
object
1 property
BreakMovedNotification
object
3 properties
BookingMovingNotification
object
3 properties
SlotBookingNotification
object
3 properties
LicenseNumber
object
2 properties
Addresses
object
1 property
BreakRemovedNotification
object
3 properties
AddressServiceNotification
object
5 properties
AddressServiceCreatedNotification
object
3 properties
InsuranceNotification
object
4 properties
BreakNotification
object
3 properties
AddressUnassignedNotification
object
3 properties
BookingPaymentStatusChangedNotification
object
3 properties
Address
object
10 properties
VisitBookingRequestNotification
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

znanylekarz-api-notification-callbacks-api-openapi.yml Raw ↑

Other APIs ZnanyLekarz publishes across the network.

ZnanyLekarz Addresses 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
ZnanyLekarz Slots API
Where this information came from

This is an independent, third-party profile of ZnanyLekarz API Notification Callbacks 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.