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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
University of California, Davis

PEAKS (CAES) — KeySerials API

The KeySerials resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Sciences Computing Resources Unit builds and runs at peaks.ucdavis.edu. 11 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries in this file split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis's own software — source at github.com/ucdavis/Peaks under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key issued to a campus team.

Documentation Provider Profile APIs.io OpenAPI GitHub

PEAKS (CAES) — KeySerials API is one of 20 APIs that University of California, Davis publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include KeySerials, peaks, and Campus Operations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 11 operations across 11 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://peaks.ucdavis.edu.

11 operations 11 paths 29 schemas 7 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://peaks.ucdavis.edu
Authentication
API Key
Contact
Application Support
License
MIT
Resource Areas
1

Authentication & Security 1

PEAKS (CAES) — KeySerials API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Auth-Token (ApiKey).

  • ApiKey — API Key Authentication

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 7 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

KeySerials 11
GET
/api/{teamName}/KeySerials/Search
Get api by team name key serials search
getApiByTeamNameKeySerialsSearch 3 params → 200401403
GET
/api/{teamName}/KeySerials/SearchInKey
Get api by team name key serials search in key
getApiByTeamNameKeySerialsSearchInKey 4 params → 200401403
GET
/api/{teamName}/KeySerials/GetForKey
Get api by team name key serials get for key
getApiByTeamNameKeySerialsGetForKey 3 params → 200401403
GET
/api/{teamName}/KeySerials/GetForPerson
Get api by team name key serials get for person
getApiByTeamNameKeySerialsGetForPerson 3 params → 200401403
GET
/api/{teamName}/KeySerials/Details/{id}
Get api by team name key serials details by id
getApiByTeamNameKeySerialsDetailsById 3 params → 200401403
POST
/api/{teamName}/KeySerials/Create
Create api by team name key serials create
postApiByTeamNameKeySerialsCreate 2 params body → 200401403
POST
/api/{teamName}/KeySerials/Update/{id}
Create api by team name key serials update by id
postApiByTeamNameKeySerialsUpdateById 3 params body → 200401403
POST
/api/{teamName}/KeySerials/Assign
Create api by team name key serials assign
postApiByTeamNameKeySerialsAssign 2 params body → 200401403
POST
/api/{teamName}/KeySerials/Revoke/{id}
Create api by team name key serials revoke by id
postApiByTeamNameKeySerialsRevokeById 3 params → 200401403
GET
/api/{teamName}/KeySerials/GetHistory/{id}
Takes the top 5 history records
getApiByTeamNameKeySerialsGetHistoryById 4 params → 200401403
GET
/api/{teamName}/KeySerials/ListKeySerialStatus
Get api by team name key serials list key serial status
getApiByTeamNameKeySerialsListKeySerialStatus 2 params → 200401403

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are Person (27 properties), History (22 properties), Equipment (20 properties), Space (18 properties). Each schema is shown below with its type and property counts.

AccessAssignment
object
14 properties
UpdateKeySerialViewModel
object
3 properties 2 required
EquipmentAttribute
object
5 properties
Key
object
11 properties 2 required
Document
object
17 properties 1 required
KeySerial
object
14 properties 2 required
WorkstationAttribute
object
5 properties
TeamPpsDepartment
object
5 properties 2 required
User
object
9 properties 3 required
History
object
22 properties 1 required
EquipmentAssignment
object
13 properties
Equipment
object
20 properties 1 required
GroupXTeam
object
5 properties 2 required
Workstation
object
14 properties 2 required
TeamApiCode
object
4 properties 1 required
Person
object
27 properties 3 required
Role
object
3 properties 1 required
AssignKeySerialViewModel
object
3 properties
WorkstationAssignment
object
13 properties
CreateKeySerialViewModel
object
4 properties 1 required
Team
object
13 properties 2 required
Group
object
4 properties 1 required
Space
object
18 properties
FinancialOrganization
object
6 properties 3 required
GroupPermission
object
5 properties 2 required
Access
object
9 properties 1 required
KeyXSpace
object
5 properties 2 required
TeamPermission
object
7 properties 3 required
KeySerialAssignment
object
14 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uc-davis-keyserials-api-openapi.yml Raw ↑

Other APIs University of California, Davis publishes across the network.

UC Davis Shibboleth Identity Provider (SAML 2.0 / InCommon)
AE Profile APIs.io
UC Davis Health FHIR R4 endpoint
AE Profile APIs.io
IET Middleware Web Service APIs
AE Profile APIs.io
UC Davis Health Systems Integration APIs
AE Profile APIs.io
CAES ACE API
AE Profile APIs.io
PEAKS (CAES) — Access API
AE Profile APIs.io
PEAKS (CAES) — Documents API
AE Profile APIs.io
PEAKS (CAES) — Equipment API
AE Profile APIs.io
PEAKS (CAES) — Keys API
AE Profile APIs.io
PEAKS (CAES) — People API
AE Profile APIs.io
PEAKS (CAES) — PeopleAdmin API
AE Profile APIs.io
PEAKS (CAES) — Spaces API
AE Profile APIs.io
#KeySerials#peaks#Campus Operations
← Back to P APIs
API Details
ID
uc-davis:uc-davis-keyserials-api
Base URL
https://peaks.ucdavis.edu
Docs
https://computing.caes.ucdavis.edu/documentation/peaks/api
Provider
University of California, Davis
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=uc-davis-keyserials-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/uc-davis-keyserials-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of PEAKS (CAES) — KeySerials API, 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.