Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Z Zentrum der Projekte
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • system
  • Zentrum der Projekte
  • Issues
  • #24
Closed
Open
Issue created Oct 05, 2026 by Hermann Hartenthaler@HartenthalerDeveloper

Public provider catalogue endpoint for GeMeDa integrations

The GeMeDa portal currently keeps its metasearch provider list in frontend code. External clients such as the webtrees module need a stable, public source for the available provider identifiers and labels.

Please provide and document a public endpoint that returns the current provider catalogue, including:

  • a stable technical provider ID;
  • a display name;
  • the existing metasearch ID where applicable;
  • clear caching and update semantics.

The endpoint should not require an authentication key because it exposes only provider metadata. This avoids stale, duplicated provider lists in integrations.

Assignee
Assign to
Time tracking

Impressum | Datenschutz