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

Utrecht University stats API

The stats API from Utrecht University — 4 operation(s) for stats.

Utrecht University stats API is one of 21 APIs that Utrecht University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Stats. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 4 operations across 4 paths, and defines 1 schema. It is described by OpenAPI 3.0.0, at version 2.1.0.

Requests are made against a single base URL, https://portal.yoda.test/api.

4 operations 4 paths 1 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2.1.0
Base URL
https://dspace.library.uu.nl/server/oai/request
Authentication
API Key, HTTP Basic
Resource Areas
1

Authentication & Security 2

Utrecht University stats API declares 2 security schemes for authenticating requests. An API key is passed in the cookie as yoda_session (cookieAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 4

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

stats 4
POST
/resource_browse_group_data
Get paginated group data groupname / size
body → 200400500
POST
/resource_full_year_differentiated_group_storage
Return the full range of registered storage data differentiated into vault/research/revision/total.
body → 200400500
POST
/resource_category_stats
Collect storage stats of last month for categories. Storage is summed up for each category.
body → 200400500
POST
/resource_monthly_category_stats
Collect storage stats for all twelve months based upon categories a user is datamanager of.
body → 200400500

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is result_error (3 properties). Each schema is shown below with its type and property counts.

result_error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

utrecht-stats-api-openapi.yml Raw ↑

Other APIs Utrecht University publishes across the network.

Utrecht University Repository OAI-PMH
Utrecht University admin API
Utrecht University browse API
Utrecht University data_access_token API
Utrecht University datarequest API
Utrecht University folder API
Utrecht University groups API
Utrecht University meta API
Utrecht University meta_form API
Utrecht University notifications API
Utrecht University provenance API
Utrecht University publication_troubleshoot API
Where this information came from

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