How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
University of Washington website screenshot

University of Washington

The University of Washington (UW) is a public research university in Seattle, Washington, United States, and one of the few higher-education institutions in this catalog that genuinely engineers and operates its own API estate rather than only buying one. UW-IT's Enterprise Web Services (EWS) programme publishes a browsable service registry and institution-authored OpenAPI descriptions for the Student Web Service (SWS v5), the IdCard Web Service (IdCardWS v1), the Groups Web Service (GWS 2.3.x at groups.uw.edu), the Identity Registration Web Service (IRWS v2 and v3) and the Token Authentication Web Service (TAWS v2) — every one of them hosted on a University of Washington registrable domain, so the operator is the institution and not a platform vendor. The honest limit matters as much as the footprint: the specifications and Swagger UIs are public, but essentially every data resource behind them is gated by UW NetID (Microsoft Entra ID OIDC), an X.509 InCommon client certificate and named ASTRA authorisation roles, and the IRWS and TAWS runtimes are not reachable from the public internet at all. UW additionally operates two open, unauthenticated machine-readable surfaces of real value — an OAI-PMH 2.0 endpoint over the ResearchWorks DSpace 9.2 repository, and a signed SAML 2.0 / Shibboleth identity-provider metadata document registered in InCommon as urn:mace:incommon:washington.edu. No central open-data portal (data.uw.edu / data.washington.edu do not resolve) and no free public developer programme were found.

agent aware

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.

Kin Score

API Evangelist profiles University of Washington the way a machine reads it — 74 machine-readable artifacts across 6 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 Washington scores 39.9/100 (developing), with a separate agent-readiness read of 28/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Behind a wall

Why this profile is thin

The University of Washington genuinely operates its own API estate — six UW-IT Enterprise Web Services with institution-authored OpenAPI descriptions on University of Washington registrable domains. What is NOT open is the data. Specifications and Swagger UIs return 200 unauthenticated, but every SWS/IdCardWS data resource 302s to UW NetID sign-in through Microsoft Entra ID, DSpace REST item retrieval returns 401, and the IRWS and TAWS runtimes do not answer from the public internet at all. Two surfaces ARE open and were verified live: the ResearchWorks OAI-PMH 2.0 endpoint and the signed Shibboleth / InCommon SAML metadata document. No open-data portal exists (data.uw.edu and data.washington.edu do not resolve) and no self-service developer programme was found — access is institutional, requested through UW-IT, and authorised by named ASTRA roles. The 26 per-resource SWS/IdCardWS entries in apis[] are OUR refine step's split of TWO institution contracts, not 26 independent APIs; x-service groups them. Removed 22 pointers to wiki.cac.washington.edu: the whole host times out on connect (curl 28), so the SWS Confluence space UW's own registry links to is dead.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is University of Washington's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.

What we probed
  • https://webservices.washington.edu/service/browse/index.htmlHTTP 200
  • https://ws.admin.washington.edu/student/swagger/v5/swagger.jsonHTTP 200
  • https://ws.admin.washington.edu/student/v5/campus.jsonHTTP 302
  • https://iam-tools.u.washington.edu/apis/gws/api.yamlHTTP 200
  • https://iam-tools.u.washington.edu/apis/irwsv3/irwsv3.yamlHTTP 200
  • https://iam-tools.u.washington.edu/apis/tawsv2/tawsv2.yamlHTTP 200
  • https://mango.u.washington.edu:646/registry/v2/personHTTP 0
  • https://digital.lib.washington.edu/server/oai/request?verb=IdentifyHTTP 200
  • https://digital.lib.washington.edu/server/apiHTTP 200
  • https://digital.lib.washington.edu/server/api/core/itemsHTTP 401
  • https://idp.u.washington.edu/metadata/idp-metadata.xmlHTTP 200
  • https://data.uw.edu/HTTP 0
  • https://data.washington.edu/HTTP 0
  • https://wiki.cac.washington.edu/display/SWSHTTP 0

If this is out of date, tell us on the provider's repo and we will re-run the profile.

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 Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
University of Washington Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from University of Washington'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-washington/"
   title="University of Washington on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/university-of-washington.svg"
       alt="University of Washington Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile University of Washington

Each block below is one kind of artifact we hold for University of Washington. 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 32

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.

Identity Registration Web Service (IRWS)

The UW-IT Identity Registry REST API. V3 (28 paths) and V2 (13 paths) OpenAPI descriptions are published openly by UW at iam-tools.u.washington.edu and are saved here; the runti...

UW-IT Enterprise Web Services Registry

Enterprise Web Services (EWS) is UW-IT's secure collection of REST/SOAP web services that let enterprise business applications access commonly shared source data in a scalable, ...

UW Groups Web Service (GWS)

The University of Washington Group Service API — UW-IT's institution-operated group registry and membership service. UW publishes the OpenAPI itself, with an explicit termsOfSer...

UW Token Authentication Web Service (TAWS)

UW-IT's Token Authentication Web Service V2 — the institution-operated issuer for the AccessToken credential that the Student and IdCard Web Services accept. Three paths; the Op...

UW Shibboleth Identity Provider (InCommon)

UW's Shibboleth identity provider publishes signed SAML 2.0 metadata at a stable URL — entityID urn:mace:incommon:washington.edu, scope washington.edu, InCommon registration ID ...

ResearchWorks Repository (DSpace REST + OAI-PMH)

ResearchWorks is UW Libraries' institutional repository, running DSpace 9.2 on UW's own host. The DSpace REST root document is public (HTTP 200) and item retrieval is gated (HTT...

Student Web Service (SWS) Campus API

Student Web Service (SWS) Campus API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS v...

IdCard Web Service (IdCardWS) Card API

IdCard Web Service (IdCardWS) Card API — a resource of the UW-IT IdCard Web Service, split out per resource by the API Evangelist refine step from the institution-published IdCa...

Student Web Service (SWS) College API

Student Web Service (SWS) College API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS ...

Student Web Service (SWS) Course API

Student Web Service (SWS) Course API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS v...

Student Web Service (SWS) Curriculum API

Student Web Service (SWS) Curriculum API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published S...

Student Web Service (SWS) Degree API

Student Web Service (SWS) Degree API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS v...

Student Web Service (SWS) Degree Audit API

Student Web Service (SWS) Degree Audit API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published...

Student Web Service (SWS) Degree Audit Exception API

Student Web Service (SWS) Degree Audit Exception API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution...

Student Web Service (SWS) Degree Audit Program API

Student Web Service (SWS) Degree Audit Program API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-p...

Student Web Service (SWS) Degree Audit Status API

Student Web Service (SWS) Degree Audit Status API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-pu...

Student Web Service (SWS) Department API

Student Web Service (SWS) Department API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published S...

Student Web Service (SWS) Enrollment API

Student Web Service (SWS) Enrollment API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published S...

Student Web Service (SWS) Enrollment Major API

Student Web Service (SWS) Enrollment Major API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-publi...

Student Web Service (SWS) Major Students API

Student Web Service (SWS) Major Students API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-publish...

Student Web Service (SWS) Notice API

Student Web Service (SWS) Notice API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS v...

Student Web Service (SWS) Person API

Student Web Service (SWS) Person API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS v...

Student Web Service (SWS) Personal Financial API

Student Web Service (SWS) Personal Financial API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-pub...

IdCard Web Service (IdCardWS) Photo API

IdCard Web Service (IdCardWS) Photo API — a resource of the UW-IT IdCard Web Service, split out per resource by the API Evangelist refine step from the institution-published IdC...

Student Web Service (SWS) Program API

Student Web Service (SWS) Program API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS ...

Student Web Service (SWS) Registration API

Student Web Service (SWS) Registration API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published...

UW Enterprise Web Services Resource List API

UW Enterprise Web Services Resource List API — a discovery resource published at the root of both the Student Web Service and the IdCard Web Service. Per-path servers[] in the s...

Student Web Service (SWS) Schedule API

Student Web Service (SWS) Schedule API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS...

Student Web Service (SWS) Section API

Student Web Service (SWS) Section API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS ...

Student Web Service (SWS) Term API

Student Web Service (SWS) Term API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published SWS v5 ...

Student Web Service (SWS) Test Score API

Student Web Service (SWS) Test Score API — a resource of the UW-IT Student Web Service, split out per resource by the API Evangelist refine step from the institution-published S...

UW Enterprise Web Services Version API

UW Enterprise Web Services Version API — a discovery resource published at the root of both the Student Web Service and the IdCard Web Service. Per-path servers[] in the specifi...

Scroll within the panel for all 32 ·

Open Collections 27

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 COLLECTION

Scroll within the panel for all 27 ·

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.

FinOps 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.

University Of Washington Context

6 classes · 3 properties

JSON-LD

Spectral Rules 2

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.

University of Washington API Rules

5 rules · 3 warnings

SPECTRAL

University of Washington API Rules

6 rules · 1 errors · 3 warnings

SPECTRAL

JSON Schema 2

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.

Course

16 properties

JSON SCHEMA

Photo

11 properties

JSON SCHEMA

JSON Structure 2

JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.

JSON Structure definitions describing this provider's data shapes.

University Of Washington Course Structure

16 properties

JSON STRUCTURE

University Of Washington Photo Structure

11 properties

JSON STRUCTURE

Examples 2

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.

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

University Of Washington Agentic Access

56 operations · 5 acting · 1 human-in-the-loop

56 operations · 5 acting

AGENTIC

Resources

Every other property we hold for University of Washington — 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 3

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

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 2

Tutorials, courses, talks, and written guidance

Operate 2

Status, limits, changes, and where to get help

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/university-of-washington · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of University of Washington, 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.