UCSB Campus API Gateway

The single API front door for the campus, at api.ucsb.edu. Every campus API is published as a proxy on it and it enforces the ucsb-api-key application entitlement before a request reaches a backend web service. It runs on Apigee (api.ucsb.edu CNAMEs to ucsb-prod.apigee.net) but the domain, the proxies, the API products and the backend services are UCSB’s, so this is institution-operated infrastructure on a vendor runtime, not a vendor tenancy. Probed live 2026-08-30: an unauthenticated call returns 401 with an Apigee fault envelope, and the CORS allow-list advertises the whole auth surface — ucsb-api-key, ucsb-api-version, ucsb-user-jwt.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/campus-api-gateway"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: ucsb:campus-api-gateway
name: UCSB Campus API Gateway
description: 'The single API front door for the campus, at api.ucsb.edu. Every campus API is published
  as a proxy on it and it enforces the ucsb-api-key application entitlement before a request reaches a
  backend web service. It runs on Apigee (api.ucsb.edu CNAMEs to ucsb-prod.apigee.net) but the domain,
  the proxies, the API products and the backend services are UCSB’s, so this is institution-operated infrastructure
  on a vendor runtime, not a vendor tenancy. Probed live 2026-08-30: an unauthenticated call returns 401
  with an Apigee fault envelope, and the CORS allow-list advertises the whole auth surface — ucsb-api-key,
  ucsb-api-version, ucsb-user-jwt.'
humanURL: https://developer.ucsb.edu/docs/security/overview
baseURL: https://api.ucsb.edu
x-operator: institution
tags:
- API Gateway
- Campus
- Security
properties:
- type: Documentation
  url: https://developer.ucsb.edu/docs/security/overview
- type: Authentication
  url: authentication/ucsb-authentication.yml
- type: Scopes
  url: scopes/ucsb-scopes.yml
- type: Errors
  url: errors/ucsb-problem-types.yml
- type: Rules
  url: rules/ucsb-rules.yml
- type: Lifecycle
  url: lifecycle/ucsb-lifecycle.yml
- type: Conformance
  url: conformance/ucsb-conformance.yml
- type: Vocabulary
  url: vocabulary/ucsb-vocabulary.yml