generated: '2026-09-05' method: searched source: https://integrations.docplanner.com/guide/fundamentals/authorization.html summary: types: - oauth2 oauth2_flows: - clientCredentials schemes: - name: oauth2 type: oauth2 flows: - flow: clientCredentials tokenUrl: https://www.{domain}/oauth/v2/token scopes: 1 description: '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 include a valid access token. `NOTE! Our SSO Api version is v2 while our Integration Api version is v3` You can get a token for testing purposes with cURL ``` curl -u {client_id}:{client_secret} https://www.{domain}/oauth/v2/token -d ''grant_ty' sources: - openapi/znanylekarz-integrations-api.yml docs: https://integrations.docplanner.com/guide/fundamentals/authorization.html derived_from: openapi/znanylekarz-integrations-api.yml note: 'Single-scheme API: OAuth 2.0 client_credentials only. No API-key header, no HTTP Basic on the resource endpoints, no mutual TLS, no OpenID Connect. Credentials are issued per integration partner through a manual onboarding, so there is no self-service key. Verified live on 2026-09-05: an unauthenticated GET of https://www.znanylekarz.pl/api/v3/integration/facilities returns HTTP 401 with {"message":"Authentication credentials could not be found."}' token_endpoint_resolved: https://www.znanylekarz.pl/oauth/v2/token token_endpoint_templated: https://www.{domain}/oauth/v2/token token_lifetime_seconds: 3600 token_type: bearer refresh_token: false request_header: 'Authorization: Bearer {access_token}' token_exchange: HTTP Basic — curl -u {client_id}:{client_secret} ... -d grant_type=client_credentials&scope=integration sso_version_note: '"NOTE! Our SSO Api version is v2 while our Integration Api version is v3" — the token endpoint lives under /oauth/v2/ while the API lives under /api/v3/.' self_service: false credential_issuance: gated: true audience: medical software providers sandbox_first: true contact: integrations@docplanner.com source: https://integrations.docplanner.com/guide/integration-process.html discovery: openid_configuration: false oauth_authorization_server: false note: No RFC 8414 authorization-server metadata and no OpenID Connect discovery document is served on any host — both 404. The token endpoint is discoverable only by reading the OpenAPI securityScheme, which means an agent cannot bootstrap auth from /.well-known/. live_probe: url: https://www.znanylekarz.pl/api/v3/integration/facilities status: 401 body: '{"message":"Authentication credentials could not be found."}' checked: '2026-09-05'