University of Wisconsin-Madison
The University of Wisconsin-Madison is a public land-grant research university in Madison, Wisconsin, and one of the very few institutions in this cohort that genuinely operates an API program of its own rather than pointing at a vendor's. Its Division of Information Technology (DoIT) runs a formal API Program on a UW-owned Google Apigee organization (doit-ipt-apigee-prod-ce29), fronted by a public developer portal at developer.wisc.edu, and publishes eleven OpenAPI 3.0 contracts — 245 operations across Person, HR, Manifest (Grouper groups), Finance, Locations, Enterprise Billing and OAuth — every one of them served from api.wisc.edu or mock.api.wisc.edu with a wisc.edu contact. Nothing in this repository is a vendor contract running under the institution's name: there is no Figshare, Pure, Ex Libris, Dataverse or Symplectic surface attributed here. Beyond the gateway, UW-Madison operates a fully public unauthenticated course-search API at public.enroll.wisc.edu, its own Shibboleth identity provider at login.wisc.edu speaking both SAML 2.0 and OpenID Connect, and a live OAI-PMH 2.0 endpoint for the MINDS@UW institutional repository. The honest limits: production access is gated behind a manual institutional approval per API product and is effectively closed to anyone without a UW NetID, the estate declares zero OAuth scopes, no contract carries a license or terms of service, and the developer portal is a client-rendered single-page app that returns an identical 2,138-byte shell for every URL — including ones that do not exist. Learning management runs on a Canvas tenant, recorded here as a tenant relationship and not as UW-Madison engineering.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles University of Wisconsin-Madison the way a machine reads it — 64 machine-readable artifacts across 12 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 — University of Wisconsin-Madison scores 56.0/100 (strong), with a separate agent-readiness read of 32/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from University of Wisconsin-Madison'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/university-of-wisconsin-madison/"
title="University of Wisconsin-Madison on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-wisconsin-madison.svg"
alt="University of Wisconsin-Madison Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-wisconsin-madison/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-wisconsin-madison/"
title="University of Wisconsin-Madison on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-wisconsin-madison/card.svg"
alt="University of Wisconsin-Madison 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 University of Wisconsin-Madison
Each block below is one kind of artifact we hold for University of Wisconsin-Madison. 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 42
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.
Locations API
Campus location, building and room reference data. 3 operations, OAuth 2.0 client credentials, maintained by the DoIT EBS/IBS API team (locations-api@doit.wisc.edu).
UW-Madison Identity Provider (Shibboleth)
Institution-operated Shibboleth IdP at login.wisc.edu, machine-readable on two protocols and almost never catalogued for a university. https://login.wisc.edu/idp/shibboleth retu...
MINDS@UW OAI-PMH Endpoint
Live OAI-PMH 2.0 harvesting endpoint for MINDS@UW, UW-Madison's institutional repository. Confirmed with ?verb=Identify — repositoryName 'MINDS@UW', protocolVersion 2.0, adminEm...
Curricular Data Model
UW-Madison's curricular data model (v1.5), published as generated Javadoc-style reference documentation on the DoIT WAMS host. Verified live and genuinely institution-operated, ...
Canvas LMS (tenant)
UW-Madison's learning management system runs on an Instructure Canvas tenant at canvas.wisc.edu, gated behind the institution's own Shibboleth IdP — an unauthenticated request 3...
University of Wisconsin-Madison Academic Units API
The Academic Units API from University of Wisconsin-Madison — 2 operation(s) for academic units.
University of Wisconsin-Madison Academic Appointments API
The academicAppointments API from University of Wisconsin-Madison — 1 operation(s) for academicappointments.
University of Wisconsin-Madison Addresses API
The addresses API from University of Wisconsin-Madison — 1 operation(s) for addresses.
University of Wisconsin-Madison Affiliations API
The affiliations API from University of Wisconsin-Madison — 1 operation(s) for affiliations.
University of Wisconsin-Madison Aggregate API
The Aggregate API from University of Wisconsin-Madison — 1 operation(s) for aggregate.
University of Wisconsin-Madison Billing Batch Delete API
The Billing Batch Delete API from University of Wisconsin-Madison — 1 operation(s) for billing batch delete.
University of Wisconsin-Madison Billing Batch Information API
The Billing Batch Information API from University of Wisconsin-Madison — 1 operation(s) for billing batch information.
University of Wisconsin-Madison Billing Batches API
The Billing Batches API from University of Wisconsin-Madison — 1 operation(s) for billing batches.
University of Wisconsin-Madison Billing Customers API
The BillingCustomers API from University of Wisconsin-Madison — 1 operation(s) for billingcustomers.
University of Wisconsin-Madison Bulk Job Failed Results API
The Bulk Job Failed Results API from University of Wisconsin-Madison — 1 operation(s) for bulk job failed results.
University of Wisconsin-Madison Bulk Job Status API
The Bulk Job Status API from University of Wisconsin-Madison — 1 operation(s) for bulk job status.
University of Wisconsin-Madison Bulkjob BillingTrans API
The Bulkjob BillingTrans API from University of Wisconsin-Madison — 1 operation(s) for bulkjob billingtrans.
University of Wisconsin-Madison Certificates API
The certificates API from University of Wisconsin-Madison — 2 operation(s) for certificates.
University of Wisconsin-Madison Degrees API
The degrees API from University of Wisconsin-Madison — 1 operation(s) for degrees.
University of Wisconsin-Madison Email Addresses API
The emailAddresses API from University of Wisconsin-Madison — 1 operation(s) for emailaddresses.
University of Wisconsin-Madison Exports API
The exports API from University of Wisconsin-Madison — 2 operation(s) for exports.
University of Wisconsin-Madison Groups API
The groups API from University of Wisconsin-Madison — 3 operation(s) for groups.
University of Wisconsin-Madison Identifiers API
The identifiers API from University of Wisconsin-Madison — 1 operation(s) for identifiers.
University of Wisconsin-Madison Jobs API
The jobs API from University of Wisconsin-Madison — 5 operation(s) for jobs.
University of Wisconsin-Madison Journals API
The Journals API from University of Wisconsin-Madison — 4 operation(s) for journals.
University of Wisconsin-Madison Members API
The members API from University of Wisconsin-Madison — 2 operation(s) for members.
University of Wisconsin-Madison Names API
The names API from University of Wisconsin-Madison — 2 operation(s) for names.
University of Wisconsin-Madison Organization Structures API
The organizationStructures API from University of Wisconsin-Madison — 2 operation(s) for organizationstructures.
University of Wisconsin-Madison Other API
The Other API from University of Wisconsin-Madison — 32 operation(s) for other.
University of Wisconsin-Madison People API
The people API from University of Wisconsin-Madison — 2 operation(s) for people.
University of Wisconsin-Madison Phone Numbers API
The phoneNumbers API from University of Wisconsin-Madison — 1 operation(s) for phonenumbers.
University of Wisconsin-Madison Research API
The Research API from University of Wisconsin-Madison — 6 operation(s) for research.
University of Wisconsin-Madison Salary Structures API
The Salary Structures API from University of Wisconsin-Madison — 2 operation(s) for salary structures.
University of Wisconsin-Madison Social Security Numbers API
The socialSecurityNumbers API from University of Wisconsin-Madison — 1 operation(s) for socialsecuritynumbers.
University of Wisconsin-Madison Standard Job Descriptions API
The Standard Job Descriptions API from University of Wisconsin-Madison — 3 operation(s) for standard job descriptions.
University of Wisconsin-Madison Supervisory Organizations API
The Supervisory Organizations API from University of Wisconsin-Madison — 2 operation(s) for supervisory organizations.
University of Wisconsin-Madison Terms API
The Terms API from University of Wisconsin-Madison — 1 operation(s) for terms.
University of Wisconsin-Madison Token API
The Token API from University of Wisconsin-Madison — 1 operation(s) for token.
University of Wisconsin-Madison UW Madison Public Course Search API
The UW Madison Public Course Search API API from University of Wisconsin-Madison — 1 operation(s) for uw madison public course search api.
University of Wisconsin-Madison Webhooks API
The webhooks API from University of Wisconsin-Madison — 7 operation(s) for webhooks.
University of Wisconsin-Madison Wiscard API
The wiscard API from University of Wisconsin-Madison — 1 operation(s) for wiscard.
University of Wisconsin-Madison Worktags API
The Worktags API from University of Wisconsin-Madison — 31 operation(s) for worktags.
Scroll within the panel for all 42 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate 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.
University Of Wisconsin Madison Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 11
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Enterprise Billing API data model
JSON SCHEMAHR API data model
JSON SCHEMALocations API data model
JSON SCHEMAManifest API data model
JSON SCHEMAMock HR API data model
JSON SCHEMAMock Manifest API data model
JSON SCHEMAMock Person API data model
JSON SCHEMAMock Person API data model
JSON SCHEMAOAuth data model
JSON SCHEMAPerson API data model
JSON SCHEMAScroll within the panel for all 11 ·
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
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 University of Wisconsin-Madison — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/university-of-wisconsin-madison · machine-readable index on apis.io
This is an independent, third-party profile of University of Wisconsin-Madison, 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.