Nursa
Nursa is a healthcare staffing marketplace, founded in Salt Lake City in 2019, that connects credentialed per diem (PRN) clinicians — registered nurses, licensed practical nurses, certified nursing assistants, certified medication aides and allied professionals — directly with hospitals, skilled nursing facilities, long-term and post-acute care providers, removing the traditional staffing agency from the middle. Facilities post open shifts and set their own rates, clinicians browse and request shifts, and both sides settle through Nursa's shift-report flow. Nursa publishes a Public API V2 (REST, JWT bearer, with an OpenID Connect / OAuth 2.0 authorization server) so workforce-management and scheduling platforms can post shifts, review requests, schedule clinicians, read clinician credentials and subscribe to webhooks — the integration surface behind its Covr, StaffLion, Dropstat, Maple and UKG partnerships. The company is accredited by The Joint Commission and reports more than 4,500 facilities and 500,000 clinicians nationwide.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Nursa the way a machine reads it — 35 machine-readable artifacts across 14 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 — Nursa scores 58.0/100 (strong), with a separate agent-readiness read of 48/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.
Put this on your own site. The badge is drawn live from Nursa's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/nursa/"
title="Nursa on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/nursa.svg"
alt="Nursa Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/nursa/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/nursa/"
title="Nursa on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/nursa/card.svg"
alt="Nursa Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Nursa
Each block below is one kind of artifact we hold for Nursa. 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 14
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.
Nursa Authorization Server
Nursa's OpenID Connect / OAuth 2.0 authorization server. Issues the JWT access tokens the Nursa Public API requires, supports the authorization code (with and without PKCE), res...
Nursa Clinicians API
The Clinicians API from Nursa — 4 operation(s) for clinicians.
Nursa Downloads API
The Downloads API from Nursa — 1 operation(s) for downloads.
Nursa Facilities API
The Facilities API from Nursa — 8 operation(s) for facilities.
Nursa Facilities webhooks API
The Facilities webhooks API from Nursa — 2 operation(s) for facilities webhooks.
Nursa Licenses API
The Licenses API from Nursa — 1 operation(s) for licenses.
Nursa Marketplace API
The Marketplace API from Nursa — 6 operation(s) for marketplace.
Nursa Scheduled shifts API
The Scheduled shifts API from Nursa — 2 operation(s) for scheduled shifts.
Nursa Shift reports API
The Shift reports API from Nursa — 4 operation(s) for shift reports.
Nursa Shift requests API
The Shift requests API from Nursa — 2 operation(s) for shift requests.
Nursa Shifts API
The Shifts API from Nursa — 1 operation(s) for shifts.
Nursa Support API
The Support API from Nursa — 1 operation(s) for support.
Nursa User webhooks API
The User webhooks API from Nursa — 2 operation(s) for user webhooks.
Nursa Webhook logs API
The Webhook logs API from Nursa — 1 operation(s) for webhook logs.
Scroll within the panel for all 14 ·
Open Collections 14
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONNursa Public API V2 Clinicians API
OPEN COLLECTIONNursa Public API V2 Downloads API
OPEN COLLECTIONNursa Public API V2 Facilities API
OPEN COLLECTIONNursa Public API V2 Facilities webhooks API
OPEN COLLECTIONNursa Public API V2 Licenses API
OPEN COLLECTIONNursa Public API V2 Marketplace API
OPEN COLLECTIONNursa Public API V2 Scheduled shifts API
OPEN COLLECTIONNursa Public API V2 Shift reports API
OPEN COLLECTIONNursa Public API V2 Shift requests API
OPEN COLLECTIONNursa Public API V2 Shifts API
OPEN COLLECTIONNursa Public API V2 Support API
OPEN COLLECTIONNursa Public API V2 User webhooks API
OPEN COLLECTIONNursa Public API V2 Webhook logs API
OPEN COLLECTIONScroll within the panel for all 14 ·
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.
nursa-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Nursa Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Nursa Public Api V2 Webhooks
ASYNCAPISecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Nursa — 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 6
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/nursa · machine-readable index on apis.io
This is an independent, third-party profile of Nursa, 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.