Collectionspace service rest based apis
1 / 14

CollectionSpace Service REST-based APIs - PowerPoint PPT Presentation

  • Uploaded on
  • Presentation posted in: General

CollectionSpace Service REST-based APIs. June 2009 Face-to-face Aron Roberts U.C. Berkeley IST/Data Services. Agenda. Overview : REST in 3 slides Summary : REST-based APIs proposed for the Services Layer Request : Feedback (later-on). REST … in 1 slide ….

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.

Download Presentation

CollectionSpace Service REST-based APIs

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript

CollectionSpace ServiceREST-based APIs

June 2009 Face-to-face

Aron Roberts

U.C. Berkeley IST/Data Services


  • Overview: REST in 3 slides

  • Summary: REST-based APIsproposed for the Services Layer

  • Request: Feedback (later-on)


REST … in 1 slide …

  • “… resources are just consistent mappings from an identifier [such as a URL path] to some set of views on server-side state.

  • “If one view doesn’t suit your needs, then feel free to create a different resource that provides a better view …

  • “These views need not have anything to do with how the information is stored on the server … [They just need] to be understandable (and actionable) by the recipient.” – Roy T. Fielding


REST … in 2 slides …

Every resource is URL-addressable:



You can get creative!




REST … in 3 slides …

To change system state, simply change a resource.

Within the /collectionobjects “bucket”, you can:

• Create an item

• Update an item with new data

• Delete an item


RESTful APIs (proposed)

Create  POST a new item to a “bucket”

POST /collectionobjects

Read  GET an item by its ID

GET /collectionobjects/{id}

Read (multiple)  GET the items in a “bucket”

GET /collectionobjects


RESTful APIs (proposed)

Read (multiple)  GET the items in a “bucket”

GET /collectionobjects

Need to define details of:

• IDs – CSIDs, museum numbers

• Filtering – child resources, query parameters

• Paging

• Formats returned – URLs, full records


RESTful APIs (proposed)

Update  PUT a fully updated item to an ID

PUT /collectionobjects/{id}

(Partial updates not REST-defined, however.)

Delete  DELETE an item by its ID

GET /collectionobjects/{id}

Resource discovery  GET a schema

GET /collectionobjects/schema(Others needed?)


RESTful APIs (proposed)

Search  Not REST-defined. Often:

GET /collectionobjects?q=term

Need to define:

• “Simple” search

•Fully-specified search

– Resource-oriented

– Query parameters

– Forms submission


RESTful APIs (proposed)

Search  (cont’d)

If we model searches as resources:

Create POST a new search

POST /searches

Read GET search results

GET /searches/{id}/results

Searches might thus be saved, shared …


Status Codes

HTTP status codes returned in the response header:

  • 200 OK The resource was read, updated, or deleted.

  • 201 Created  The resource was created.

  • 400 Bad Request  The data sent in the request was bad.

  • 403 Not Authorized  The Principal named in the request was not authorized to perform this action.

  • 404 Not Found  The resource does not exist.

  • 409 Conflict  A duplicate resource could not be created.

  • 500 Internal Server Error  A service error occurred.


Error Responses

Response in body when a 4xx or 5xx status is returned:


<code>Mandatory code</code>

<message>Optional message</message>

<resource-id>Resource ID, if available</resource-id>

<request-uri>URI of request</request-uri>



More info

REST-based APIs

Common System Specific Elements

(payloads, error messages, and more!)



  • Eagerly invited. (Probably later on!)

  • We seek consistency, and to share ideas, with other CollectionSpace teams re REST-based APIs.


  • Login