h3 { background-color: #eee; padding: 0.6em; }
#content .code { margin-left: 2.5em!important; background-color: #fafafa!important; }
.pdl .syntaxhighlighter table td.code .container, .syntaxhighlighter .line.alt2, .syntaxhighlighter .line.alt1 { background-color: #fafafa!important; }

Overview

Introduction

The Fedora 4 HTTP API is generally a RESTful API. HTTP methods like GET, PUT, POST and DELETE are implemented on most resource paths. The API also relies heavily on content negotiation to deliver context-appropriate responses, and a HATEOAS-driven text/html response (providing a decent GUI experience on top of the repository).

...

[...] describes the use of HTTP for accessing, updating, creating and deleting resources from servers that expose their resources as Linked Data.  It provides clarifications and extensions of the rules of Linked Data [LINKED-DATA]:

1. Use URIs as names for things
2. Use HTTP URIs so that people can look up those names
3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)
4. Include links to other URIs, so that they can discover more things

Changes planned

Asynchronous API support

Versioning

CND node types

Changelog

Endpoints

Resources

Repository objects can be loosely divided into two classes of resources:

 - Object and containers ("fedora:object"), containing RDF properties and 0 or more child nodes
 - Binaries, containing any binary payload

Objects

Request URI: /path/to/some/resource

...

Binary Content

Request URI: /path/to/some/resource/fcr:content

...

Batch Operations

Request URI: /path/to/some/resource/fcr:datastreams

...

Export / Import

Request URI: /path/to/some/resource

...

Versioning

Request URI: /path/to/some/resource/fcr:versions

...

Services

Backup and Restore

Request URI: /

Methods: GET, POST

...

Identifiers 

Request URI: /path/to/some/resource/fcr:identifier

...

Transactions

Request URI: /fcr:tx; /path/to/transaction/fcr:tx

...

Fixity

Request URI: /path/to/some/resource/fcr:fixity

...

Workspaces

Request URI: /fcr:workspaces/(workspace name)

...

Content Modeling

Request URI: /fcr:nodetypes

Methods: GET, POST

Node types

...

Namespaces

Request URI: /fcr:namespaces

...

Sitemaps

Request URI: /sitemap

Methods: GET, POST

...

Search

Full text

Request URI: /fcr:search

Methods: GET

...

SPARQL

Request URI: /fcr:sparql

Methods: GET

...