Download OpenAPI specification:Download
This is the IIIF API Specification for Digital Bodleian. We provide our manifests in both Presentation API v2 (default) and v3 (available via Content Negotiation).
Most URIs are dereferenceable, and are returned with their appropriate JSON-LD @context
when de-referenced. The only exception
to this are Ranges; this will be addressed in a future update.
The 406 Not Acceptable status code will be returned for requests that apply to a specific IIIF version. For example, Sequences have been removed in v3, so requesting a Sequence ID as a IIIFv3 response will return a 406 Status Code.
You are welcome to harvest our manifests for the purposes of indexing or making our content available in aggregator services. However, if are expecting to harvest a significant number of manifests, we would ask that you get in touch with us and let us know. You can do this by contacting our digital support team, or by adding your e-mail address to the User-Agent string.
We would prefer that you do not download and re-host our images.
We welcome bug reports. If you are having a problem retrieving or parsing our manifests, or if you find an invalid manifest, please contact us and provide the link to the manifest that does not work.
Returns a IIIF Manifest. Clients will receive a Presentation v2.1 manifest by default. Version 3.0 manifests
can be returned by sending an Accept
header with a value of application/ld+json;profile=http://iiif.io/api/presentation/3/context.json
.
Presentation API 3.0 manifests are returned with a partOf
key that contains a link to all Collections this
manifest is a member of.
manifest_id required | string <uuid> Example: b73ca01f-aac8-4916-a7c6-3c8e67939a66 The ID of the Manifest to Retrieve |
{- "@type": "sc:Manifest"
}
Dereferenced Canvases are returned with the within
key (v2) or a partOf
key (v3)
pointing to their parent manifest.
canvas_id required | string <uuid> Example: f37dd11c-a243-4b66-9a65-b8d498a114d6 The ID of the Canvas to retrieve |
{- "@id": "string",
- "@type": "sc:Canvas"
}
A dereferenced Sequence Object. Note that sequences are only available in v2 manifests, so this will return a 406 status code if it is requested for a v3 manifest. For all manifests we publish there will be only one sequence, the default.
sequence_id required | string Example: faeff7fb-f8a7-44b5-95ed-cff9a9ffd198_default The ID of the sequence |
{ }
A dereferenced Annotation Object.
annotation_id required | string <uuid> Example: f37dd11c-a243-4b66-9a65-b8d498a114d6 The Annotation ID |
{ }
A dereferenced AnnotationPage Object. Note that annotation pages are only available in v3 manifests, so this will return a 406 status code if it is requested for a v2 manifest.
annotation_page_id required | string Example: f37dd11c-a243-4b66-9a65-b8d498a114d6 The annotation page ID |
{ }
A dereferenced AnnotationList Object. Note that annotation pages are only available in v2 manifests, so this will return a 406 status code if it is requested for a v3 manifest.
annotation_list_id required | string Example: f37dd11c-a243-4b66-9a65-b8d498a114d6 The annotation list ID |
{ }
A IIIF Image API Info Response. Clients will receive a Image API v2.1 response by default. Version 3.0 responses
can be returned by sending an Accept
header with a value of application/ld+json;profile=http://iiif.io/api/image/3/context.json
.
If a request omits the /info.json
, the response will be a 307 redirect to /info.json
.
image_id required | string <uuid> Example: 082d5ad2-ea08-463c-ad50-6d1a0cb01246 The ID of the Image to retrieve |
{- "@id": "string",
- "@type": "sc:Image"
}
Supports the IIIF v2.1 and v3.0 Image API. A full Image API URL might look like:
https://iiif.bodleian.ox.ac.uk/iiif/image/1363b336-260d-4f22-a6cf-4e1320dbb689/800,1400,1550,1950/256,/0/default.jpg
This should return the following image:
image_id required | string <uuid> |
required | Full (string) or Array of Arr (integers) Image Region to return. Can be either the keyword |
required | Full (string) or Array of Arr (integers) Size of image to return. Supports the following values:
|
rotation required | integer [ 0 .. 360 ] Default: 0 Rotation angle of the returned image, specified in degrees. Only supported in 90 degree
increments. Raises a 500 error if the values are less than 0, or greater than 360. All values
may be prepended with a |
quality required | string Enum: "default" "color" "grey" "bitonal" Quality of the returned image. |
format required | string Value: "jpg" The only supported return format is |
The top-level IIIF Collection contains a list of all of the sub-collections. Harvesters and crawlers should
note that many manifests belong to two or more collections, so using this as an entry
point for retrieving all manifests will result in many duplicate records.
It is better to use the all
collection, which links directly to all manifests, or to individual collections.
{- "@id": "string",
- "@type": "sc:Collection"
}
A list of all manifests we publish, sorted by their label. This is a very large result to download.
{- "@id": "string",
- "@type": "sc:Collection"
}
Clients may use the top-level Collection endpoint to discover the URIs for all collections we publish.
collection_id required | string Example: colleges The ID of the Collection to Retrieve |
{- "@id": "string",
- "@type": "sc:Collection"
}
page-number required | string A page number, formatted as 'page-NNN', where NNN is an integer value for a page, e.g., 'page-0'. |
{ }
While individual activities for update and delete MAY be provided in the future, at present we only publish 'Create' activities
uuid required | string <uuid> An identifier of the create activity. In theory this may be any UUID; in practice, since we are only publishing Create activities, this will correspond to the UUID of the created object. |
{ }
A request for the root (https://iiif.bodleian.ox.ac.uk/) will return a JSON document containing links to top-level IIIF resources; namely the top-level collection, and a pointer to the ActivityStreams root. Root requests ("/") will return a 303 Redirect to "/info.json".
{ }