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
Universiti Sains Malaysia

USM Repository EPrints REST and Export

Anonymous read interface to Repository@USM beyond OAI-PMH, verified route by route on 2026-09-01. /rest/ exposes three datasets (eprint, user, subject); /rest/eprint/{id}.xml returns full EPrints EP2 data XML; /rest/eprint/{id}/{field}.txt gives single-field plain-text access; /rest/subject/{id}.xml walks the Library of Congress subject tree; and /cgi/export/eprint/{id}/{format}/{filename} serves seventeen verified bibliographic serializations including JSON, RDF/XML, METS, MODS, DIDL, Atom, BibTeX and RIS. One soft-404 trap is documented in the contract: /rest/eprint/{id}.json answers HTTP 200 with the repository's HTML landing page, not JSON.

Documentation Provider Profile APIs.io OpenAPI GitHub

USM Repository EPrints REST and Export is one of 6 APIs that Universiti Sains Malaysia publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Repository, REST, Research, Open Access, and Metadata. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, API documentation, and 1 JSON Schema.

This API exposes 7 operations across 7 paths, organized into 2 resource areas. It is described by OpenAPI 3.1.0, at version 3.3.16.

Requests are made against a single base URL, https://eprints.usm.my.

7 operations 7 paths 0 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.3.16
Base URL
https://eprints.usm.my
Contact
Repository@USM administrator
Resource Areas
2

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 GET. They span 2 resource areas: Repository, Export. Each is listed below with its method, path, parameters, and response codes.

Repository 6

EPrints REST dataset and record access.

GET
/rest/
List the REST datasets exposed by the repository
listDatasets → 200
GET
/rest/eprint/
List every eprint id in the repository
listEprints → 200
GET
/rest/eprint/{eprintid}.xml
Get one record as EPrints EP2 data XML
getEprintXml 1 param → 200
GET
/rest/eprint/{eprintid}/documents.xml
Get the document (file) set attached to a record
getEprintDocuments 1 param → 200
GET
/rest/eprint/{eprintid}/{field}.txt
Get a single metadata field as plain text
getEprintField 2 params → 200
GET
/rest/subject/{subjectid}.xml
Get one subject-classification node as EP2 XML
getSubject 1 param → 200
Export 1

EPrints export plugins — one bibliographic serialization per format.

GET
/cgi/export/eprint/{eprintid}/{format}/{filename}
Export one record in a named bibliographic format
exportEprint 3 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

usm-repository-eprints-rest-openapi.yml Raw ↑

Other APIs Universiti Sains Malaysia publishes across the network.

USM Repository OAI-PMH
AE Profile APIs.io
USM Shibboleth Identity Provider (SIFULAN / eduGAIN)
AE Profile APIs.io
e-Learning@USM Moodle Web Services
AE Profile APIs.io
Crossref membership — Universiti Sains Malaysia
AE Profile APIs.io
ROR record — Universiti Sains Malaysia
AE Profile APIs.io
#Repository#REST#Research#Open Access#Metadata#EPrints#Bibliographic
← Back to U APIs
API Details
ID
usm:eprints-rest
Base URL
https://eprints.usm.my
Docs
https://eprints.usm.my/rest/
Provider
Universiti Sains Malaysia
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=eprints-rest-2&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/eprints-rest-2"

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 USM Repository EPrints REST and Export, 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.