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

University of Vienna Data Stream API

Requests for transforming and validating datastreams

University of Vienna Data Stream API is one of 20 APIs that University of Vienna publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Datastream. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.

This API exposes 24 operations across 24 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 3.0.

Requests are made against 2 base URLs: https://services.phaidra.univie.ac.at/api/, https://sandbox.phaidra.org/api/.

24 operations 24 paths 12 schemas 2 GET22 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0
Base URL
https://phaidra.univie.ac.at/api/oai/
Authentication
API Key, HTTP Basic
License
Resource Areas
1

Authentication & Security 2

University of Vienna Data Stream API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-XSRF-TOKEN (tokenAuth). It accepts HTTP basic authentication (basicAuth).

Paths & Operations 24

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

Data Stream 24

Requests for transforming and validating datastreams

GET
/uwmetadata/tree
Get uwmetadata structure
getUwmetadataTree → 200
POST
/uwmetadata/json2xml
Transforms uwmetadata JSON to XML
postUwmetadataJson2xml body → 200
POST
/uwmetadata/xml2json
Transforms uwmetadata XML to JSON
postUwmetadataXml2json 1 param body → 200
POST
/uwmetadata/validate
Validates uwmetadata XML
postUwmetadataValidate body → 200400
POST
/uwmetadata/json2xml_validate
Validates JSON uwmetadata
postUwmetadataJson2xmlValidate body → 200400
GET
/mods/tree
Get MODS tree
getModsTree → 200
POST
/mods/json2xml
Transforms MODS JSON to XML
postModsJson2xml body → 200
POST
/mods/xml2json
Transforms MODS XML to JSON
postModsXml2json 1 param body → 200
POST
/mods/validate
Validates the MODS XML
postModsValidate body → 200
POST
/mods/json2xml_validate
Validates MODS JSON
postModsJson2xmlValidate body → 200400
POST
/rights/json2xml
Transforms rights JSON to XML
postRightsJson2xml body → 200
POST
/rights/xml2json
Transforms rights XML to JSON
postRightsXml2json body → 200
POST
/rights/validate
Validates rights XML
postRightsValidate body → 200
POST
/rights/json2xml_validate
Validates rights JSON
postRightsJson2xmlValidate body → 200400
POST
/geo/json2xml
Transforms the geo JSON to XML
postGeoJson2xml body → 200
POST
/geo/xml2json
Transforms geo XML to JSON
postGeoXml2json body → 200
POST
/geo/validate
Validates the geo XML
postGeoValidate body → 200
POST
/geo/json2xml_validate
Validates the geo JSON
postGeoJson2xmlValidate body → 200400
POST
/members/order/json2xml
Transforms members JSON to XML
postMembersOrderJson2xml body → 200
POST
/members/order/xml2json
Transforms the members XML structure to JSON
postMembersOrderXml2json body → 200
POST
/annotations/json2xml
Transforms annotations JSON to XML
postAnnotationsJson2xml body → 200
POST
/annotations/xml2json
Transforms annotations XML to JSON
postAnnotationsXml2json body → 200
POST
/annotations/validate
Validates the annotations XML
postAnnotationsValidate body → 200
POST
/annotations/json2xml_validate
Validates the annotations JSON
postAnnotationsJson2xmlValidate body → 200400

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are vocabularies_mapping (118 properties), vocabularies (44 properties), mods_tree (6 properties), default (2 properties). Each schema is shown below with its type and property counts.

vocabularies
object
44 properties
vocabularies_mapping
object
118 properties
members
array
default
object
2 properties
annotations
object
1 property
uwmetadata_min
array
uwmetadata_article_basic
object
rights
object
1 property
uwmetadata
array
geo
object
1 property
mods_tree
object
6 properties
mods
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-vienna-data-stream-api-openapi.yml Raw ↑

Other APIs University of Vienna publishes across the network.

PHAIDRA OAI-PMH Endpoint
PHAIDRA directory API (University of Vienna)
PHAIDRA imageserver API (University of Vienna)
PHAIDRA lists API (University of Vienna)
PHAIDRA misc API (University of Vienna)
PHAIDRA oai-pmh API (University of Vienna)
PHAIDRA object-advanced API (University of Vienna)
PHAIDRA object-basics API (University of Vienna)
PHAIDRA relationships API (University of Vienna)
PHAIDRA search API (University of Vienna)
PHAIDRA session API (University of Vienna)
PHAIDRA stats API (University of Vienna)
Where this information came from

This is an independent, third-party profile of University of Vienna Data Stream 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.