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

Taylor's Library Koha REST API

REST API of the Taylor's University Library catalog, served under /api/v1 by a Koha integrated library system that Taylor's self-hosts (librarycatalogue.taylors.edu.my resolves through librarycatalogue.wip.taylors.edu.my to 103.145.154.51, Taylor's own infrastructure — no vendor CNAME). The live Swagger 2.0 definition is publicly retrievable and describes 213 paths across 76 tags with 113 definitions; its info.contact is the Koha Development Team, so the DEPLOYMENT is Taylor's and the CONTRACT is the Koha community's. The OpenAPI documents registered here are a verified subset covering only the six resources whose object schemas were confirmed present in the live definition (patron, checkout, hold, item, library, item_type); they are refine-split per tag and are recorded as one surface, not six, because they describe one deployment. Collection and resource endpoints require authentication (HTTP 401 to anonymous clients); the specification document itself is public.

Taylor’s Library Koha REST API is one of 7 APIs that Taylor’s University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Library, Library Catalog, Koha, and REST. The published artifact set on APIs.io includes an API reference, API documentation, an OpenAPI specification, a JSON-LD context, and 6 JSON Schemas.

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

Requests are made against a single base URL, https://librarycatalogue.taylors.edu.my/api/v1.

2 operations 2 paths 2 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://librarycatalogue.taylors.edu.my/api/v1
Authentication
HTTP Basic, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Taylor's Library Koha REST API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It supports OAuth 2.0 (oauth2ClientCredentials) using the clientCredentials flow. By default, every request must be authenticated.

Paths & Operations 2

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

patrons 2

Patron (borrower) records

GET
/patrons
List patrons
listPatrons → 200401403
GET
/patrons/{patron_id}
Get patron
getPatron 1 param → 200401404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are patron (29 properties), error (2 properties). Each schema is shown below with its type and property counts.

patron
object
29 properties 4 required
error
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

taylors-patrons-api-openapi.yml Raw ↑

Other APIs Taylor's University publishes across the network.

Taylor's Library OAI-PMH
Taylor's e-Repository DSpace CRIS REST API
Taylor's e-Repository OAI-PMH
Taylor's University Identity Federation (Microsoft Entra ID)
Taylor's University Crossref Membership
Taylor's University ROR Registration
Where this information came from

This is an independent, third-party profile of Taylor's Library Koha REST 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.