Table of Contents
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).
The Fedora 4 RDF-based responses may be serialized as:
- application/ld+json
- application/n-triples
- application/rdf+xml
- text/n3 (or text/rdf+n3)
- text/plain
- text/turtle (or application/x-turtle)
The text/html response also includes embedded RDFa markup.
The API is based loosely around the Linked Data Platform 1.0 Architecture, which:
[...] 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]:
- Use URIs as names for things
- Use HTTP URIs so that people can look up those names
- When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL)
- Include links to other URIs, so that they can discover more things
Note: Fedora doesn't currently support blank nodes.
Changes planned
- Asynchronous API support
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 (roughly corresponding to Fedora 3 datastreams)
Objects
Binary Content
Batch Operations
Export and Import
Request URI: /path/to/some/resource/fcr:export
Methods: GET, POST
Exporting large trees of resources may fail because of memory limitations. Exporting 250,000 simple objects (only the system-defined properties) was successful and resulted in a 400MB export file, but exporting larger sets of resources failed. To work around this limitation, you can segment your repository (for example, into several top-level directories each containing 250,000 or fewer resources) and export each top-level directory as a separate export file.
Objects are exported and imported relative to the request URI path given. By default, the exported jcr/xml won't contain any subtrees and binary contents.
E.g., if you run:
curl "http://localhost:8080/rest/path/to/resource/fcr:export" > export.xml curl -X POST --data-binary "@export.xml" "http://localhost:8080/rest/somewhere/else"
The resource with no subtree and binary content will be imported to http://localhost:8080/rest/somewhere/else/resource.
GET fcr:export Retrieve serialized form of a resource. By default, no subtree and binary content will be exported
Request Headers:
FORMAT Export formats; the exact formats available depend on the repository configuration.
Parameters:
recurse: To export subtree with its value set to true. For example, recurse=true. Default is false.
skipBinary: To export binary content with its value set to false. For example, skipBinary=false. Default is true.
The export formats that are available are shown as properties on resources, e.g. this resource exports jcr/xml:
<> <http://fedora.info/definitions/v4/rest-api#exportsAs> <./fcr:export?format=jcr/xml> ;
Example:
To export a resource with no subtree and no binary content:
curl "http://localhost:8080/rest/path/to/some/resource/fcr:export"
To export a resource with subtree and binary content:
curl "http://localhost:8080/rest/path/to/some/resource/fcr:export?recurse=true&skipBinary=false"
Response:
Status: 200 Headers: Content-Type: application/xml Body: <sv:node xmlns:dc="http://purl.org/dc/terms/" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" xmlns:ns001="http://purl.org/dc/elements/1.1/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:test="info:fedora/test/" xmlns:image="http://www.modeshape.org/images/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fedorarelsext="http://fedora.info/definitions/v4/rels-ext#" xmlns:mix="http://www....
Status:
200 OK: if the resource is exported successfully
404 Not Found: if the resource does not exist
POST fcr:import Import a serialized resource
Request Headers:
FORMAT Import formats. The exact formats available depend on the repository configuration.
CONTENT-LOCATION (Optional) A URI to a resource to use instead of the request body
Example:
curl -X POST --data-binary "@export.xml" "http://localhost:8080/rest/path/to/some/fcr:import?format=jcr/xml" Body: <sv:node xmlns:dc="http://purl.org/dc/terms/" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" xmlns:ns001="http://purl.org/dc/elements/1.1/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:test="info:fedora/test/" xmlns:image="http://www.modeshape.org/images/1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fedorarelsext="http://fedora.info/definitions/v4/rels-ext#" xmlns:mix="http://www....
Response:
Status: 201 Created Headers: Location: http://localhost:8080/rest/path/to/some/resource/
Status:
201 No Content: if the resource is imported successfully
404 Not Found: if the path does not exist
409 Conflict: if a node with the same UUID exists
Response:
Item already exists
Locking
Versioning
Request URI: /path/to/some/resource/fcr:versions
Methods: GET, POST, PATCH
GET Get a list of the available versions of an object
Request Headers:
ACCEPT application/ld+json, application/n-triples, application/rdf+xml, application/x-turtle, application/xhtml+xml, application/xml, text/html, text/n3, text/plain, text/rdf+n3, text/turtle
Example:
curl -H "Accept: text/turtle" http://localhost:8080/rest/path/to/resource/fcr:versions
Response:
Status: 200 OK Headers: Content-Type: text/turtle Body: <http://localhost:8080/rest/path/to/resource> fedora:hasVersion <http://localhost:8080/rest/path/to/resource/fcr:versions/87a0a8c317f1e749515d33-cb73-4fd7-9d1d-c715eb6947e0> . <http://localhost:8080/rest/path/to/resource/fcr:versions/87a0a8c317f1e749515d33-cb73-4fd7-9d1d-c715eb6947e0> fedora:hasVersionLabel "v0"^^<http://www.w3.org/2001/XMLSchema#string> ; fedora:created "2014-12-03T23:55:38.47Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> . <http://localhost:8080/rest/path/to/resource> fedora:hasVersion <http://localhost:8080/rest/path/to/resource/fcr:versions/87a0a8c317f1e7dae533ec-b1b6-4da1-8bb9-f1964e253572> . <http://localhost:8080/rest/path/to/resource/fcr:versions/87a0a8c317f1e7dae533ec-b1b6-4da1-8bb9-f1964e253572> fedora:hasVersionLabel "v1"^^<http://www.w3.org/2001/XMLSchema#string> ; fedora:created "2014-12-03T23:56:12.863Z"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
Status:
200 OK
404 Not Found: This resource is not versioned or this resource is not exist.
Response: The requested resource is not available.
GET Get a previous version of an object
Request Headers:
ACCEPT application/ld+json, application/n-triples, application/rdf+xml, application/x-turtle, application/xhtml+xml, application/xml, text/html, text/n3, text/plain, text/rdf+n3, text/turtle
Example:
curl http://localhost:8080/rest/resource/fcr:versions/<version-label>
Response:
Status: 200 OK Response Headers: ETag: "39f0d8a01a066771e56f70be892a39a7b505843c" Last-Modified: Tue, 20 May 2014 19:29:10 GMT Content-Type: text/turtle Body: <http://localhost:8080/rest/resource/fcr:versions/87a0a8c317f1e72c658170-624d-40f9-96cb-21ede3392155> <http://fedora.info/definitions/v4/repository#primaryType> "nt:frozenNode"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://fedora.info/definitions/v4/repository#frozenPrimaryType> "nt:folder"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://fedora.info/definitions/v4/repository#created> "2014-05-20T19:29:00.192Z"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://fedora.info/definitions/v4/repository#frozenMixinTypes> "fedora:resource"^^<http://www.w3.org/2001/XMLSchema#string> , "mix:versionable"^^<http://www.w3.org/2001/XMLSchema#string> , "fedora:object"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://fedora.info/definitions/v4/repository#lastModified> "2014-05-20T19:29:10.555Z"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://fedora.info/definitions/v4/repository#frozenUuid> "fed529c6-2121-4b1d-83fc-cc4274563612"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://fedora.info/definitions/v4/repository#lastModifiedBy> "bypassAdmin"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://fedora.info/definitions/v4/repository#uuid> "87a0a8c317f1e72c658170-624d-40f9-96cb-21ede3392155"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://fedora.info/definitions/v4/repository#createdBy> "bypassAdmin"^^<http://www.w3.org/2001/XMLSchema#string> ; a <http://www.jcp.org/jcr/nt/1.0frozenNode> , <http://www.jcp.org/jcr/nt/1.0base> , <http://www.jcp.org/jcr/mix/1.0referenceable> .
Status:
200 OK
404 Not Found: if the version or the resource does not exist
Response: The requested resource is not available.
POST Create a new version of an object
Request Headers
SLUG (Required) A suggested name for the new child resource, which the repository may ignore.
Example:
curl -X POST -H "Slug: newVersionName" http://localhost:8080/rest/path/to/resource/fcr:versions
Response:
Status: 204 No Content
Status:
204 No Content: if a new version is created successfully
404 Not Found: if the resource does not exist
409 Conflict: if the version label is already in use for another version of this rexource
Response: The requested resource is not available.
PATCH Revert to a previous version of an object
Example:
curl -X PATCH http://localhost:8080/rest/path/to/resource/fcr:versions/existingVersionName
Response:
Status: 204 No Content
Status:
204 No Content: if the version is reverted successfully
404 Not Found: if the version does not exist
Response: The requested resource is not available.
Request URI: /path/to/some/resource/fcr:versions/versionName
Methods: DELETE
DELETE Remove a previous version of an object
Example:
curl -X DELETE http://localhost:8080/rest/path/to/resource/fcr:versions/versionName
Response:
Status: 204 No Content
Trying to delete the current version of a resource will result in an error. To revert to an old version of a resource, first revert to the old version using the PATCH method, and then delete the newer version.
Status:
204 No Content: if the version is reverted successfully
400 Bad Request: if trying to delete the most recent version
Response: Cannot remove current version
404 Not Found: if the version does not exist
Response: The requested resource is not available.
Services
Access Roles
Request URI: /path/to/some/resource/fcr:accessroles
Methods: GET, POST, DELETE
Arbitrary access roles may be set through this API. However, they are only enforced when paired with a Policy Enforcement Point that is aware of access roles.
GET Get a list of all the roles assigned to principals on this resource
Output formats: application/json
Query Parameters:
EFFECTIVE When supplied, gets the list of effective roles for this resource, including those inherited from the parent
Example:
curl "http://localhost:8080/rest/49/3d/24/41/493d2441-0541-41c7-a23b-09d1f17d4a0f/fcr:accessroles"
Response:
Status: 200 OK Headers: Content-Type: application/json Transfer-Encoding: chunked Server: Jetty(8.1.11.v20130520) Body: {"principal name 3":["admin"],"principal name 1":["reader"],"principal name 2":["writer"]}
Status:
200 OK: if access roles retrieved successfully
204 No Content: if access roles not assigned
404 Not Found: if the resource doesn't exist
POST Set the roles assigned on this resource
Request Headers:
CONTENT-TYPE application/json
Example:
curl -X POST -H "Content-Type: application/json" --data-binary "@post.txt" "http://localhost:8080/rest/49/3d/24/41/493d2441-0541-41c7-a23b-09d1f17d4a0f/fcr:accessroles" Body: { "principal name 1" : [ "reader" ], "principal name 2" : [ "writer" ], "principal name 3" : [ "admin" ] }
Response:
Status: 201 Created Headers: Location: http://localhost:8080/rest/49/3d/24/41/493d2441-0541-41c7-a23b-09d1f17d4a0f/fcr:accessroles Content-Length: 0 Server: Jetty(8.1.11.v20130520)
Status:
201 Created: if the access roles were created successfully
400 Bad Request: if there was an error processing the access roles declaration
415 Unsupported Media Type: if the Content-Type of the uploaded content isn't application/json
DELETE Clear all roles assignments from this resource
Example:
curl -X DELETE "http://localhost:8080/rest/49/3d/24/41/493d2441-0541-41c7-a23b-09d1f17d4a0f/fcr:accessroles"
Response:
Status: 204 No Content Headers: Server: Jetty(8.1.11.v20130520)
Status:
204 No Content: if the access roles are deleted successfully
404 Not Found: if the resource doesn't exist
Backup and Restore
Request URI: /
Methods: GET, POST
POST fcr:backup Initiate a (consistent) backup of the repository
The backup will be stored in a temporary directory on the server. As yet, there is not a REST API method for retrieving the content of the backup.
Example:
curl -X POST "http://localhost:8080/rest/fcr:backup"
Response:
Status: 200 OK Body: /tmp/fcrepo4-data/path/to/backup/directory
Status:
200 OK
POST fcr:restore Replace repository content with data from a backup directory
Example:
curl -X POST --data-binary "/tmp/fcrepo4-data/path/to/backup/directory" "http://localhost:8080/rest/fcr:restore"
Response:
Status: 204 No Content
Status:
204 Backup restored
500 Error restoring backup
Fixity
Request URI: /path/to/some/resource/fcr:fixity
Methods: GET
GET Get the fixity report for an object
Checking fixity requires retrieving the content from the binary store and may take some time.
Request Headers:
ACCEPT application/ld+json, application/n-triples, application/rdf+xml, application/x-turtle, application/xhtml+xml, application/xml, text/html, text/n3, text/plain, text/rdf+n3, text/turtle
Example:
curl -H "Accept: text/turtle" "http://localhost:8080/rest/path/to/some/resource/fcr:fixity"
Response (fixity success):
Status: 200 OK Headers: Content-Type: text/turtle Body: <http://localhost:8080/rest/path/to/some/resource#fixity/1400589459772> a <http://www.loc.gov/premis/rdf/v1#Fixity> . <http://localhost:8080/rest/path/to/some/resource> <http://www.loc.gov/premis/rdf/v1#hasFixity> <http://localhost:8080/rest/path/to/some/resource#fixity/1400589459772> . <http://localhost:8080/rest/path/to/some/resource#fixity/1400589459772> <http://www.loc.gov/premis/rdf/v1#hasContentLocation> <info://org.modeshape.jcr.value.binary.FileSystemBinaryStore@7bcc39fb/fcrepo4/fcrepo-webapp/fcrepo4-data/fcrepo.binary-store-path#f7d787ee7fc58ce7fc257ae0067a2c65476be750> . <info://org.modeshape.jcr.value.binary.FileSystemBinaryStore@7bcc39fb/fcrepo4/fcrepo-webapp/fcrepo4-data/fcrepo.binary-store-path#f7d787ee7fc58ce7fc257ae0067a2c65476be750> a <http://www.loc.gov/premis/rdf/v1#ContentLocation> ; <http://www.loc.gov/premis/rdf/v1#hasContentLocationValue> "info://org.modeshape.jcr.value.binary.FileSystemBinaryStore@7bcc39fb/fcrepo4/fcrepo-webapp/fcrepo4-data/fcrepo.binary-store-path#f7d787ee7fc58ce7fc257ae0067a2c65476be750"^^<http://www.w3.org/2001/XMLSchema#string> .
Response (fixity failure):
Status: 200 OK Headers: Content-Type: text/turtle Body: <http://localhost:8080/rest/path/to/some/resource#fixity/1400589459772> a <http://www.loc.gov/premis/rdf/v1#Fixity> . <http://localhost:8080/rest/path/to/some/resource> <http://www.loc.gov/premis/rdf/v1#hasFixity> <http://localhost:8080/rest/path/to/some/resource#fixity/1400589459772> . <http://localhost:8080/rest/path/to/some/resource#fixity/1400589459772> <http://www.loc.gov/premis/rdf/v1#hasContentLocation> <info://org.modeshape.jcr.value.binary.FileSystemBinaryStore@7bcc39fb/fcrepo4/fcrepo-webapp/fcrepo4-data/fcrepo.binary-store-path#f7d787ee7fc58ce7fc257ae0067a2c65476be750> . <http://localhost:8080/rest/path/to/some/resource#fixity/1400589459772> <http://fedora.info/definitions/v4/repository#status> "BAD_CHECKSUM"^^<http://www.w3.org/2001/XMLSchema#string> , "BAD_SIZE"^^<http://www.w3.org/2001/XMLSchema#string> ; <http://www.loc.gov/premis/rdf/v1#hasMessageDigest> <urn:sha1:b04bded0d83b74ac0c700945e24e43e823eb5821> ; <http://www.loc.gov/premis/rdf/v1#hasSize> "1324943"^^<http://www.w3.org/2001/XMLSchema#int> .
Status:
200 OK
404 Resource not found
Identifiers
Namespaces
Node Types
Request URI: /fcr:nodetypes
Methods: GET
GET get a list of registered types (as RDFS triples)
Request
Request Headers:
ACCEPT application/ld+json, application/n-triples, application/rdf+xml, application/x-turtle, application/xhtml+xml, application/xml, text/html, text/n3, text/plain, text/rdf+n3, text/turtle
Example:
curl "http://localhost:8080/rest/fcr:nodetypes"
Response:
Status: 200 OK Headers: Content-Type: text/turtle Body: <http://fedora.info/definitions/v4/rest-api#object> a <http://www.w3.org/2000/01/rdf-schema#Class> ; <http://www.w3.org/2000/01/rdf-schema#label> "fedora:object" ; <http://www.w3.org/2000/01/rdf-schema#subClassOf> <http://fedora.info/definitions/v4/rest-api#resource> . <http://fedora.info/definitions/v4/rest-api#resource> a <http://www.w3.org/2000/01/rdf-schema#Class> ; <http://www.w3.org/2000/01/rdf-schema#label> "fedora:resource" ; <http://www.w3.org/2000/01/rdf-schema#subClassOf> <http://fedora.info/definitions/v4/rest-api#relations> , <http://www.jcp.org/jcr/mix/1.0created> , <http://www.jcp.org/jcr/mix/1.0lastModified> , <http://www.jcp.org/jcr/mix/1.0lockable> , <http://www.jcp.org/jcr/mix/1.0versionable> . [...]
Status:
200 OK
Search
Sitemaps
Transactions
Request URI: /fcr:tx; /tx:{transaction_id}/path/to/resource, /tx:{transaction_id}/fcr:tx, /tx:{transaction_id}/fcr:commit, /tx:{transaction_id}/fcr:rollback
Methods: GET, POST
GET Get the current status of the repository in a transaction
Example:
curl -i "http://localhost:8080/rest/tx:86dd0891-d975-42d8-8837-a24ad6041b59"
Response:
Status: 200 OK Link: <http://localhost:8080/rest/>;rel="canonical" Body: Same as non-transaction response.
Status:
200 OK: If the request was successful
410 Gone: Transaction not found
POST Create a new transaction
After retrieving a transaction resource, the client can execute any REST API method prefixed by the transaction location.
Transactions are automatically closed and rolled back after 3 minutes of inactivity. Transactions can be refreshed by POSTing to /rest/{tx:id}/fcr:tx
Example:
curl -i -X POST "http://localhost:8080/rest/fcr:tx"
Response:
Status: 201 Created Headers: Location: http://localhost:8080/rest/tx:83e34464-144e-43d9-af13-b3464a1fb9b5 Expires: Sat, 16 Nov 2013 00:32:57 GMT
Usage:
When a transaction has been created, it will return a Location header. Use this location as the base URL for performing REST API operations within the transaction. When you are done with the transaction, either append "/fcr:tx/fcr:commit" to commit the transaction to the repository or "/fcr:tx/fcr:rollback" to discard the changes.
curl -X POST "http://localhost:8080/rest/tx:83e34464-144e-43d9-af13-b3464a1fb9b5/path/to/object/to/create" curl -X DELETE "http://localhost:8080/rest/tx:83e34464-144e-43d9-af13-b3464a1fb9b5/path/to/resource/to/delete" curl -X POST "http://localhost:8080/rest/tx:83e34464-144e-43d9-af13-b3464a1fb9b5/fcr:tx/fcr:commit"
Status:
201 Created: if the transaction is created successfully
POST Keep an existing transaction alive
Example:
curl -i -X POST "http://localhost:8080/rest/tx:83e34464-144e-43d9-af13-b3464a1fb9b5/fcr:tx"
Response:
Status: 204 No Content Headers: Location: http://localhost:8080/rest/tx:83e34464-144e-43d9-af13-b3464a1fb9b5 Expires: Sat, 16 Nov 2013 03:35:43 GMT
Status:
204 No Content: if the transaction is renewed successfully
410 Gone: if the transaction doesn't exist
POST Save and commit an open transaction
Any operations you made within the scope of the transaction will be applied together, meaning if any of them fail, the whole transaction will fail.
Example:
curl -i -X POST "http://localhost:8080/rest/tx:123456789/fcr:tx/fcr:commit"
Response:
Status: 204 No Content
Status:
204 No Content: if the transaction is committed successfully
410 Gone: if the transaction doesn't exist
POST Rollback and close an open transaction
Example:
curl -i -X POST "http://localhost:8080/rest/tx:123456789/fcr:tx/fcr:rollback"
Response:
Status: 204 No Content
Status:
204 No Content: if the transaction is discarded successfully
410 Gone: if the transaction doesn't exist
Transform
Request URI: /fcr:transform/{program}
Methods: GET, POST
GET get a resource transformed with the default transform
Request Headers:
Example:
@prefix fedora : <http://fedora.info/definitions/v4/repository#> id = . :: xsd:string ; title = dc:title :: xsd:string; uuid = fedora:uuid :: xsd:string ;
curl "http://localhost:8080/rest/49/3d/24/41/493d2441-0541-41c7-a23b-09d1f17d4a0f/fcr:transform/default"
Response:
Status: 200 OK Headers: Content-Type: application/json Transfer-Encoding: chunked Server: Jetty(8.1.11.v20130520) Body: [{"id":["http://localhost:8080/rest/49/3d/24/41/493d2441-0541-41c7-a23b-09d1f17d4a0f"],"title":[],"uuid":["07630a24-5a0b-4ba7-80ab-0691f68667ce"]}]
Status:
200 OK: if the transform is applied successfully
400 Bad Request: if the program doesn't exist
404 Not Found: if the resource doesn't exist
Note
To reference a stored "program" in the GET form of the fcr:transform service, the LDPath transformation directive must be stored at the following path:
http://localhost:8080/rest/fedora:system/fedora:transform/fedora:ldpath/<program-name>/<resource-type>
Where <program-name> can be any name, and <resource-type> is the type of Fedora resource on which the transform will be applied:
- "fedora:Container"
- "fedora:nonRdfSourceDescription"
- "fedora:Resource"
Example:
- Store a new program.
curl -i -X PUT -H "Content-Type: application/rdf+ldpath" --data-binary "@post.txt" http://localhost:8080/rest/fedora:system/fedora:transform/fedora:ldpath/newprogram/fedora:Container
Response
Status 201 Created Headers: Content-Type: text/plain http://localhost:8080/rest/fedora:system/fedora:transform/fedora:ldpath/newprogram/fedora:Container
2. Get a resource transformed with the stored transform
curl -i http://localhost:8080/rest/pid5/fcr:transform/newprogram
Response
Status 200 OK Header: Server: Apache-Coyote/1.1 Content-Type: application/json Body: [{"id":["http://localhost:8080/rest/pid5"],"title":["some-resource-title"],"description":[],"uuid":["caa7bc6c-b80b-4e30-8ec1-15e90937e3be"]}]
POST get a resource transformed with the supplied transform
Output formats: application/json,text/tab-separated-values,text/csv,text/sse,text/plain,application/sparql-results+json,application/sparql-results+xml,application/sparql-results+bio,text/turtle,text/rdf+n3,application/N-triples,application/rdf_xml
Example:
curl -X POST -H "Content-Type: application/rdf+ldpath" --data-binary "@post.txt" "http://localhost:8080/rest/49/3d/24/41/493d2441-0541-41c7-a23b-09d1f17d4a0f/fcr:transform" Body: @prefix fcrepo : <http://fedora.info/definitions/v4/repository#> id = . :: xsd:string ; title = dc:title :: xsd:string; uuid = fcrepo:uuid :: xsd:string ;
Response:
Status: 200 OK Headers: Content-Type: application/json Transfer-Encoding: chunked Server: Jetty(8.1.11.v20130520) Body: [{"id":["http://localhost:8080/rest/49/3d/24/41/493d2441-0541-41c7-a23b-09d1f17d4a0f"],"title":[],"uuid":["07630a24-5a0b-4ba7-80ab-0691f68667ce"]}]
Status:
200 OK: if the transform is applied successfully
400 Bad Request: if there was an error parsing or processing the transform
404 Not Found: if the resources doesn't exist
Workspaces