The REST API module provides a programmatic interface to DSpace Communities, Collections, Items, and Bitstreams.
DSpace 4 introduced the initial REST API, which did not allow for authentication, and provided only READ-ONLY access to publicly accessible Communities, Collections, Items, and Bitstreams. DSpace 5 builds off of this and allows authentication to access restricted content, as well as allowing Create, Edit and Delete on the DSpace Objects. DSpace 5 REST API also provides improved pagination over resources and searching. There has been a minor drift between the DSpace 4 REST API and the DSpace 5 REST API, so client applications will need to be targeted per version.
The REST API deploys as a standard webapp for your servlet container / tomcat. For example, depending on how you deploy webapps, one way would be to alter tomcat-home/conf/server.xml and add:
<Context path="/rest" docBase="/dspace/webapps/rest" /> |
In DSpace 4, the initial/official Jersey-based REST API was added to DSpace. The DSpace 4 REST API provides READ-ONLY access to DSpace Objects.
In DSpace 5, the REST API adds authentication, allows Creation, Update, and Delete to objects, can access restricted materials if authorized, and it requires SSL.
For localhost development purposes, SSL can add additional getting-started difficulty, so security can be disabled. To disable DSpace REST's requirement to require security/ssl, alter [dspace]/webapps/rest/WEB-INF/web.xml
or [dspace-source]/dspace-rest/src/main/webapp/WEB-INF/web.xml
and comment out the <security-constraint>
block, and restart your servlet container. Production usages of the REST API should use SSL, as authentication credentials should not go over the internet unencrypted.
The REST API is modeled after the DSpace Objects of Communities, Collections, Items, and Bitstreams. The API is not a straight database schema dump of these entities, but provides some wrapping that makes it easy to follow relationships in the API output.
Note: You must set your request header's "Accept" property to either JSON (application/json) or XML (application/xml) depending on the format you prefer to work with. |
Example usage from command line in XML format with pretty printing:
curl -s -H "Accept: application/xml" http://localhost:8080/rest/communities | xmllint --format - |
Example usage from command line in JSON format with pretty printing:
curl -s -H "Accept: application/json" http://localhost:8080/rest/communities | python -m json.tool |
For this documentation, we will assume that the URL to the "REST" webapp will be http://localhost:8080/rest/ for production systems, this address will be slightly different, such as: https://demo.dspace.org/rest/. The path to an endpoint, will go after the /rest/, such as /rest/communities, all-together this is: http://localhost:8080/rest/communities
Another thing to note is that there are Query Parameters that you can tack on to the end of an endpoint to do extra things. The most commonly used one in this API is "?expand". Instead of every API call defaulting to giving you every possible piece of information about it, it only gives a most commonly used set by default and gives the more "expensive" information when you deliberately request it. Each endpoint will provide a list of available expands in the output, but for getting started, you can start with ?expand=all, to make the endpoint provide all of its information (parent objects, metadata, child objects). You can include multiple expands, such as: ?expand=collections,subCommunities .
DSpace 6.x supports pagination by allowing two query parameters: limit
and offset
. Note however that the aggregate results number is not supplied (see DS-3887). Endpoints which return arrays of objects, such as /communities, /collections or /items, are "paginated": the full list is broken into "pages" which start at offset
from the beginning of the list and contain at most limit
elements. By repeated queries you can retrieve any portion of the array or all of it. The default value of offset
is 0 and the default value of limit
is 100. So, as an example, to retrieve the sixth through tenth elements of the full list of Collections, you could do this:
curl -s -H "Accept: application/json" http://localhost:8080/rest/collections?offset=5\&limit=5 |
REST API Authentication has changed in DSpace 6.x. It now uses a |
Method | Endpoint | Description | |||
---|---|---|---|---|---|
GET | / | REST API static documentation page | |||
POST | /login | Login to the REST API using a DSpace EPerson (user). It returns a Example Request:
Example Response:
Example of using JSESSIONID cookie for subsequent (authenticated) requests:
Invalid email/password combinations will receive an Please note, special characters need to be HTTP URL encoded. | |||
GET | /shibboleth-login | Login to the REST API using Shibboleth authentication. In order to work, this requires additional Apache configuration. To authenticate, execute the following steps: 1. Call the REST Shibboleth login point with a Cookie jar:
2. This should take you again to the IdP login page. You can submit this form using curl using the same cookie jar. However this is IdP dependant so we cannot provide an example here. 3. Once you submit the form using curl, you should be taken back to the /rest/shibboleth-login URL which will return you the JSESSIONID. 4. Using that JSESSIONID, check if you have authenticated successfully:
| |||
POST | /logout | Logout from the REST API, by providing a Example Request:
After posting a logout request, cookie is invalidated and the "/status" path should show you as unauthenticated (even when passing that same cookie). For example:
Invalid token will result in HTTP 400 Invalid Request | |||
GET | /test | Returns string "REST api is running", for testing that the API is up. Example Request:
Example Response:
| |||
GET | /status | Receive information about the currently authenticated user token, or the API itself (e.g. version information). Example Request (XML by default):
Example Request (JSON):
Example JSON Response:
|
Before Shibboleth authentication for the REST API will work, you need to secure the /rest/shibboleth-login
endpoint. Add this configuration section to your Apache HTTPD Shibboleth configuration:
<Location "/rest/shibboleth-login"> AuthType shibboleth ShibRequireSession On # Please note that setting ShibUseHeaders to "On" is a potential security risk. # You may wish to set it to "Off". See the mod_shib docs for details about this setting: # https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPApacheConfig#NativeSPApacheConfig-AuthConfigOptions # Here's a good guide to configuring Apache + Tomcat when this setting is "Off": # https://www.switch.ch/de/aai/support/serviceproviders/sp-access-rules.html#javaapplications ShibUseHeaders On require valid-user </Location> |
You can test your configuration in 3 different ways:
https://dspace.myu.edu/rest/shibboleth-login
, this should redirect you to the login page of your IdP if you don't have a Shibboleth session yet./rest/shibboleth-login
URL. You should then see a blank page but in the response headers, the JSESSIONID cookie should be present./rest/status
and you should see information on the current authenticated ePerson.curl -v -L -c cookiejar "https://dspace.myu.edu/rest/shibboleth-login" |
/rest/shibboleth-login
URL which will return you the JSESSIONID.Using that JSESSIONID, check if you have authenticated successfully:
curl -v "https://dspace.myu.edu/dspace-rest/status" --cookie "JSESSIONID=0633C6379266A283E53F65DF8EF61AB9" |
_shibsession_64656661756c74687...
You can also grab this cookie from your browser.Double check that the cookie you took is valid:
curl -v 'https://dspace-url/Shibboleth.sso/Session' -H 'Cookie: _shibsession_64656661756c7468747470733a2f2f7265706f7369746f72792e636172646966666d65742e61632e756b2f73686962626f6c657468=_a8d3ad20d8b655250c7357f7ac0e2910;' |
Use this cookie to obtain a Tomcat JSESSIONID:
curl -v 'https://dspace-url/rest/shibboleth-login' -H 'Cookie: _shibsession_64656661756c7468747470733a2f2f7265706f7369746f72792e636172646966666d65742e61632e756b2f73686962626f6c657468=_a8d3ad20d8b655250c7357f7ac0e2910;' |
Use the returned JSESSIONID to check if you have authenticated successfully:
curl -v "http://dspace-url/rest/status" --cookie "JSESSIONID=0633C6379266A283E53F65DF8EF61AB9" |
Communities in DSpace are used for organization and hierarchy, and are containers that hold sub-Communities and Collections (ex: Department of Engineering).
For an alternative way to create a Community/Collection hierarchy to the REST API take a look at Importing Community and Collection Hierarchy.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /communities | Returns array of all communities. |
GET | /communities/top-communities | Returns array of all top-level communities. |
GET | /communities/{communityId} | Returns community. |
GET | /communities/{communityId}/collections | Returns array of collections of a community. |
GET | /communities/{communityId}/communities | Returns array of sub-communities of a community. |
POST | /communities | Create new community at top level. You must post community. |
POST | /communities/{communityId}/collections | Create new collections in community. You must post Collection. |
POST | /communities/{communityId}/communities | Create new sub-community in community. You must post Community. |
PUT | /communities/{communityId} | Update community. You must put Community. |
DELETE | /communities/{communityId} | Delete community. |
DELETE | /communities/{communityId}/collections/{collectionId} | Delete collection in community. |
DELETE | /communities/{communityId}/communities/{communityId2} | Delete sub-community in community. |
Collections in DSpace are containers of Items. (ex: Engineering Faculty Publications).
For an alternative way to create a Community/Collection hierarchy to the REST API take a look at Importing Community and Collection Hierarchy.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /collections | Return all collections in array. Use the limit parameter to control items per response (default 100) and offset for paging. |
GET | /collections/{collectionId} | Return collection with id. |
GET | /collections/{collectionId}/items | Return all items of collection. |
POST | /collections/{collectionId}/items | Create posted item in collection. You must post an Item. |
POST | /collections/find-collection | Find collection by passed name. |
PUT | /collections/{collectionId} | Update collection. You must put Collection. |
DELETE | /collections/{collectionId} | Delete collection from DSpace. |
DELETE | /collections/{collectionId}/items/{itemId} | Delete item in collection. |
Items in DSpace represent a "work" and combine metadata and files, known as Bitstreams.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /items | Return list of items. |
GET | /items/{item id} | Return item. |
GET | /items/{item id}/metadata | Return item metadata. |
GET | /items/{item id}/bitstreams | Return item bitstreams. |
POST | /items/find-by-metadata-field | Find items by metadata entry. You must post a MetadataEntry. |
POST | /items/{item id}/metadata | Add metadata to item. You must post an array of MetadataEntry. |
POST | /items/{item id}/bitstreams | Add bitstream to item. You must post a Bitstream. |
PUT | /items/{item id}/metadata | Update metadata in item. You must put a MetadataEntry. Each metadata entry that will replace all prior matching metadata entries, i.e. if you submit n 'dc.subject' entries all pre-existing 'dc.subject' entries in the item will be deleted and replaced with the n entries |
DELETE | /items/{item id} | Delete item. |
DELETE | /items/{item id}/metadata | Clear item metadata. |
DELETE | /items/{item id}/bitstreams/{bitstream id} | Delete item bitstream. |
Bitstreams are files. They have a filename, size (in bytes), and a file format. Typically in DSpace, the Bitstream will the "full text" article, or some other media. Some files are the actual file that was uploaded (tagged with bundleName:ORIGINAL), others are DSpace-generated files that are derivatives or renditions, such as text-extraction, or thumbnails. You can download files/bitstreams. DSpace doesn't really limit the type of files that it takes in, so this could be PDF, JPG, audio, video, zip, or other. Also, the logo for a Collection or a Community, is also a Bitstream.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /bitstreams | Return all bitstreams. |
GET | /bitstreams/{bitstream id} | Return bitstream. |
GET | /bitstreams/{bitstream id}/policy | Return bitstream policies. |
GET | /bitstreams/{bitstream id}/retrieve | Return data of bitstream. |
POST | /bitstreams/{bitstream id}/policy | Add policy to item. You must post a ResourcePolicy |
PUT | /bitstreams/{bitstream id}/data | Update data/file of bitstream. You must put the data. |
PUT | /bitstreams/{bitstream id} | Update metadata of bitstream. You must put a Bitstream, does not alter the file/data. |
DELETE | /bitstreams/{bitstream id} | Delete bitstream. |
DELETE | /bitstreams/{bitstream id}/policy/{policy_id} | Delete bitstream policy. |
You can access the parent object of a Bitstream (normally an Item, but possibly a Collection or Community when it is its logo) through: /bitstreams/:bitstreamID?expand=parent
As the documentation may state "You must post a ResourcePolicy" or some other object type, this means that there is a structure of data types, that your XML or JSON must be of type, when it is posted in the body.
In DSpace, Communities, Collections, and Items typically get minted a Handle Identifier. You can reference these objects in the REST API by their handle, as opposed to having to use the internal item-ID.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /handle/{handle-prefix}/{handle-suffix} | Returns a Community, Collection, or Item object that matches that handle. |
Assembling a full representation of the community and collection hierarchy using the communities and collections endpoints can be inefficient. Retrieve a lightweight representation of the nested community and collection hierarchy. Each node of the hierarchy contains minimal information (id, handle, name).
HTTP method | REST endpoint | Description |
---|---|---|
GET | /hierarchy | Retrieve a lightweight representation of the nested community and collection hierarchy. |
HTTP method | REST endpoint | Description |
---|---|---|
GET | /registries/schema | Return the list of schemas in the registry |
GET | /registries/schema/{schema_prefix} | Returns the specified schema |
GET | /registries/schema/{schema_prefix}/metadata-fields/{element} | Returns the metadata field within a schema with an unqualified element name |
GET | /registries/schema/{schema_prefix}/metadata-fields/{element}/{qualifier} | Returns the metadata field within a schema with a qualified element name |
GET | /registries/metadata-fields/{field_id} | Add a schema to the schema registry |
POST | /registries/schema/ | Add a metadata field to the specified schema |
POST | /registries/schema/{schema_prefix}/metadata-fields | Return the specified metadata field |
PUT | /registries/metadata-fields/{field_id} | Update the specified metadata field |
DELETE | /registries/metadata-fields/{field_id} | Delete the specified metadata field from the metadata field registry |
DELETE | /registries/schema/{schema_id} | Delete the specified schema from the schema registry |
Note: since the schema object contains no data fields, the following method has not been implemented: PUT /registries/schema/{schema_id}
Reporting Tools that allow a repository manager to audit a collection for metadata consistency and bitstream consistency. See REST Based Quality Control Reports for more information or test the Collection Report Tool or Metadata Query Tool on demo.dspace.org.
HTTP method | REST endpoint | Description |
---|---|---|
GET | /reports | Return a list of report tools built on the rest api |
GET | /reports/{nickname} | Return a redirect to a specific report |
GET | /filters | Return a list of use case filters available for quality control reporting |
GET | /filtered-collections | Return collections and item counts based on pre-defined filters |
GET | /filtered-collections/{collection_id} | Return items and item counts for a collection based on pre-defined filters |
GET | /filtered-items | Retrieve a set of items based on a metadata query and a set of filters |
Here are all of the data types, not all fields are necessary or supported when posting/putting content, but the output contains this information:
{ "id":456, "name":"Reports Community", "handle":"10766/10213", "type":"community", "link":"/rest/communities/456", "expand":["parentCommunity","collections","subCommunities","logo","all"], "logo":null, "parentCommunity":null, "copyrightText":"", "introductoryText":"", "shortDescription":"Collection contains materials pertaining to the Able Family", "sidebarText":"", "countItems":3, "subcommunities":[], "collections":[] } |
{ "id":730, "name":"Annual Reports Collection", "handle":"10766/10214", "type":"collection", "link":"/rest/collections/730", "expand":["parentCommunityList","parentCommunity","items","license","logo","all"], "logo":null, "parentCommunity":null, "parentCommunityList":[], "items":[], "license":null, "copyrightText":"", "introductoryText":"", "shortDescription":"", "sidebarText":"", "numberItems":3 } |
{ "id":14301, "name":"2015 Annual Report", "handle":"123456789/13470", "type":"item", "link":"/rest/items/14301", "expand":["metadata","parentCollection","parentCollectionList","parentCommunityList","bitstreams","all"], "lastModified":"2015-01-12 15:44:12.978", "parentCollection":null, "parentCollectionList":null, "parentCommunityList":null, "bitstreams":null, "archived":"true", "withdrawn":"false" } |
{ "id":47166, "name":"appearance and physiology 100 percent copied from wikipedia.pdf", "handle":null, "type":"bitstream", "link":"/rest/bitstreams/47166", "expand":["parent","policies","all"], "bundleName":"ORIGINAL", "description":"", "format":"Adobe PDF", "mimeType":"application/pdf", "sizeBytes":129112, "parentObject":null, "retrieveLink":"/bitstreams/47166/retrieve", "checkSum":{"value":"62778292a3a6dccbe2662a2bfca3b86e","checkSumAlgorithm":"MD5"}, "sequenceId":1, "policies":null } |
[{ "id":317127, "action":"READ", "epersonId":-1, "groupId":0, "resourceId":47166, "resourceType":"bitstream", "rpDescription":null, "rpName":null, "rpType":"TYPE_INHERITED", "startDate":null, "endDate":null }] |
{ "key":"dc.description.abstract", "value":"This is the description abstract", "language": null } |
{ "email":"test@dspace.org", "password":"pass" } |
{ "okay":true, "authenticated":true, "email":"test@dspace.org", "fullname":"DSpace Test User", "token":"6d45daaa-7b02-4ae7-86de-a960838fae5c" } |
The REST API for DSpace is implemented using Jersey, the reference implementation of the Java standard for building RESTful Web Services (JAX-RS 1). That means this API should be easier to expand and maintain than other API approaches, as this approach has been widely adopted in the industry. If this client documentation does not fully answer about how an endpoint works, it is helpful to look directly at the Java REST API code, to see how it is implemented. The code typically has required parameters, optional parameters, and indicates the type of data that will be responded.
There was no central ProviderRegistry that you have to declare your path. Instead, the code is driven by annotations, here is a list of annotations used in the code for CommunitiesResource.java:
@GET, which indicates that this method responds to GET http requests
@Consumes({ MediaType.APPLICATION_JSON, MediaType.APPLICATION_XML }), this indicates that this request expects input of either JSON or XML. Another endpoint accepts HTML input.
Property | rest.stats |
---|---|
Example Value | true |
Informational Note | Boolean value indicates whether statistics should be recorded for access via the REST API; Defaults to 'false'. |
Note that if the logging level (in the logging configuration) is set to DEBUG the REST API will output the entire transaction to the logs. In cases where changes are being made to metadata by automatic processes this can result in several gigabyte sized logs depending on the volume.
For the purpose of more accurate statistics, a web-based tool may specify who is using it, by adding parameters to the request:
http://localhost:8080/rest/items/:ID?userIP=ip&userAgent=userAgent&xforwardedfor=xforwardedfor |
If no parameters are given, the details of the HTTP request's sender are used in statistics. This enables tools to record the details of their user rather than themselves.
Additional information can be found in the README for dspace-rest, and in the GitHub Pull Request for DSpace REST (Jersey).
Usage examples can be found at: https://github.com/BrunoNZ/dspace-rest-requests