samedi · Authentication Profile

Samedi Authentication

Authentication

samedi secures its APIs with oauth2 and openIdConnect across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, clientCredentials, and refreshToken flow(s).

CompanyHealthcareSchedulingAppointmentsBookingPatient EngagementAuthenticationFHIRTelemedicineGermany

Methods: oauth2, openIdConnect Schemes: 3 OAuth flows: authorizationCode, clientCredentials, refreshToken API key in:

Security Schemes

OpenIDConnect openIdConnect

OAuth2 oauth2

· flows: authorizationCode, clientCredentials

BookingAPIOAuth oauth2

· flows: authorizationCode

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://patient.samedi.de/.well-known/openid-configuration
docs: https://wiki.samedi.de/display/doc/Booking+API
summary:
  types: [oauth2, openIdConnect]
  oauth2_flows: [authorizationCode, clientCredentials, refreshToken]
  token_endpoint_auth_methods: [client_secret_basic, client_secret_post]
notes: >-
  samedi exposes OAuth 2.0 / OpenID Connect at patient.samedi.de. Two versioned
  OAuth surfaces are documented: the OIDC provider at /oauth/* (issuer
  https://patient.samedi.de) and the Booking API OAuth at /api/auth/v2/* used by
  the official omniauth-samedi strategy. API requests are authorized with a
  Bearer access token. API credentials are requested at
  https://patient.samedi.de/api/signup.
schemes:
- name: OpenIDConnect
  type: openIdConnect
  openIdConnectUrl: https://patient.samedi.de/.well-known/openid-configuration
  issuer: https://patient.samedi.de
  id_token_signing_alg_values_supported: [RS256]
  subject_types_supported: [pairwise]
  sources: ['well-known/samedi-openid-configuration.json']
- name: OAuth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://patient.samedi.de/oauth/authorize
    tokenUrl: https://patient.samedi.de/oauth/token
  - flow: clientCredentials
    tokenUrl: https://patient.samedi.de/oauth/token
  endpoints:
    revocation_endpoint: https://patient.samedi.de/oauth/revoke
    introspection_endpoint: https://patient.samedi.de/oauth/introspect
    userinfo_endpoint: https://patient.samedi.de/oauth/userinfo
    jwks_uri: https://patient.samedi.de/oauth/discovery/keys
  sources: ['well-known/samedi-oauth-authorization-server.json']
- name: BookingAPIOAuth
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://patient.samedi.de/api/auth/v2/authorize
    tokenUrl: https://patient.samedi.de/api/auth/v2/token
  sources: ['https://github.com/samedi/omniauth-samedi']

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
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 security artifact

curl "https://apis.io/api/v1/security/samedi-authentication"

All security posture

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

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.

GitHub Google LinkedIn

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