Documentation > UOC Public API

UOC Public API

REST Resources

This API supports a Representational State Transfer (REST) model for accessing a set of resources through a fixed set of operations. The following resources are accessible through the RESTful model:

The REST resources expose a data model that is supported by a set of client-side libraries that are made available on the files and libraries page.

There is also a WADL document describing the REST API.

SOAP Endpoints

This API is exposed through a set of WSI Basic Profile -compliant SOAP v1.1 endpoints. The API supports XML-binary Optimized Pacakging (XOP) and SOAP Message Transmission Optimization Mechanism (MTOM) for transmission of binary data. The SOAP API is described by the following endpoints:

Namespace “calendar”

Namespace URI: http://api.uoc.edu/v1/subject
WSDL: calendar.wsdl

Endpoints

Namespace “calendar”

Namespace URI: http://api.uoc.edu/v1/calendar
WSDL: calendar.wsdl

Endpoints

Namespace “user”

Namespace URI: http://api.uoc.edu/v1/user
WSDL: user.wsdl

Endpoints

Namespace “people”

Namespace URI: http://api.uoc.edu/v1/people
WSDL: people.wsdl

Endpoints

Namespace “classroom”

Namespace URI: http://api.uoc.edu/v1/classroom
WSDL: classroom.wsdl

Endpoints

Namespace “mail”

Namespace URI: http://api.uoc.edu/v1/mail
WSDL: mail.wsdl

Endpoints

The SOAP API is also accessible by a set of client-side libraries that can be downloaded from the files and libraries page.

Data Model

All endpoints act on a common set of data. The data can be represented with difference media (i.e. “MIME”) types, depending on the endpoint that consumes and/or produces the data. The data can described by XML Schema, which definitively describes the XML representation of the data, but is also useful for describing the other formats of the data, such as JSON.

This document will describe the data using terms based on XML Schema. Data can be grouped by namespace, with a schema document describing the elements and types of the namespace. Generally speaking, types define the structure of the data and elements are instances of a type. For example, elements are usually produced by (or consumed by) a REST endpoint, and the structure of each element is described by its type.

Namespace “ns0″

Namespace URI: (default namespace)
XSD: ns0.xsd

Data Elements

Data Types