QGenda
QGenda is a healthcare workforce management platform used by hospitals, health systems, medical groups, and academic medical centers for physician and staff scheduling, on-call management, provider credentialing, time tracking, and clinical operations. Its public REST API (version 2) exposes 146 operations across scheduling, open shifts, rotations, staff members, tasks, time-off requests and limits, pay codes and rates, locations, credentialing, notifications, and workflows. The API uses token-based authentication via a login endpoint, serves JSON over HTTPS (TLS 1.2/1.3 only), supports BR/GZip compression, and offers OData query parameters on select resources. Backed by ICONIQ Capital.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles QGenda the way a machine reads it — 31 machine-readable artifacts across 27 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — QGenda scores 53.1/100 (developing), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile QGenda
Each block below is one kind of artifact we hold for QGenda. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 27
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
QGenda Company API
The Company API from QGenda — 1 operation(s) for company.
QGenda Contacts API
The Contacts API from QGenda — 3 operation(s) for contacts.
QGenda Corporate Entities API
The Corporate Entities API from QGenda — 2 operation(s) for corporate entities.
QGenda Credit Allocation API
The Credit Allocation API from QGenda — 2 operation(s) for credit allocation.
QGenda Daily API
The Daily API from QGenda — 6 operation(s) for daily.
QGenda Daily Case API
The Daily Case API from QGenda — 2 operation(s) for daily case.
QGenda Integration API
The Integration API from QGenda — 1 operation(s) for integration.
QGenda Location API
The Location API from QGenda — 18 operation(s) for location.
QGenda Locations API
The Locations API from QGenda — 2 operation(s) for locations.
QGenda Login API
The Login API from QGenda — 1 operation(s) for login.
QGenda Notification List API
The Notification List API from QGenda — 4 operation(s) for notification list.
QGenda Organization API
The Organization API from QGenda — 1 operation(s) for organization.
QGenda Pay Code API
The Pay Code API from QGenda — 1 operation(s) for pay code.
QGenda Pay Pool Template API
The Pay Pool Template API from QGenda — 1 operation(s) for pay pool template.
QGenda Pay Rate API
The Pay Rate API from QGenda — 2 operation(s) for pay rate.
QGenda Profile API
The Profile API from QGenda — 1 operation(s) for profile.
QGenda Request API
The Request API from QGenda — 2 operation(s) for request.
QGenda Request Limit API
The Request Limit API from QGenda — 6 operation(s) for request limit.
QGenda Schedule API
The Schedule API from QGenda — 4 operation(s) for schedule.
QGenda Staff Member API
The Staff Member API from QGenda — 27 operation(s) for staff member.
QGenda Staff Target API
The Staff Target API from QGenda — 8 operation(s) for staff target.
QGenda Support API
The Support API from QGenda — 1 operation(s) for support.
QGenda Tags API
The Tags API from QGenda — 1 operation(s) for tags.
QGenda Task API
The Task API from QGenda — 5 operation(s) for task.
QGenda Time Event API
The Time Event API from QGenda — 2 operation(s) for time event.
QGenda User API
The User API from QGenda — 4 operation(s) for user.
QGenda Workflows API
The Workflows API from QGenda — 5 operation(s) for workflows.
Scroll within the panel for all 27 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
qgenda-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for QGenda — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/qgenda · machine-readable index on apis.io