/iiif
GET /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{x-fylr-signature}/{version}/info.json
GET /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{x-fylr-signature}/{version}/info.jsonThe IIIF endpoint serves images and tiles.
Access token in the Authorization header:
Authorization: Bearer <token>.
The ID of the file.
The hash is the file.hash as described here.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs.
The file.class_extension as described here.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs. The signature will be taken from the query parameter first and if not found, from the request header.
The signature to omit file permission checks. It will be added to the URL when
retrieved through /api/db, /api/search or other endpoints which deliver
fylr URLs. The signature will be taken from the query parameter first and if
not found, from the request header.
Contains the IIIF image information.
IIIF Image API 2.0 image information document — the standard
reply to a /info.json request, defined by the IIIF Image API
2.0 specification.
fylr serves this document so any IIIF-aware client (Mirador, Universal Viewer, OpenSeadragon, ...) can discover the image's dimensions, supported tile sizes and feature profile.
JSON-LD context — always the IIIF Image API 2 URL.
The image's IIIF service URL — /info.json without the
/info.json suffix.
The IIIF protocol URI.
The image's native width, in pixels.
The image's native height, in pixels.
Access to the file is denied (code InsufficientRights):
the caller holds neither RIGHT_ASSET_SHOW nor
RIGHT_ASSET_DOWNLOAD (and no deep_link access applies), or
the request hash / version does not match the stored file,
or the x-fylr-signature is invalid or expired. This endpoint
returns no 401; a missing or invalid token is treated as an
anonymous request.
The addressed file id does not exist. A wrong hash, wrong
version, or an invalid / expired signature is a 403, not
a 404.
HEAD /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{x-fylr-signature}/{version}/info.json
HEAD /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{x-fylr-signature}/{version}/info.jsonSame access checks as GET (and the same 403 / 404
responses; there is no 401), but returns no body on success.
Access token in the Authorization header:
Authorization: Bearer <token>.
The ID of the file.
The hash is the file.hash as described here.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs.
The file.class_extension as described here.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs. The signature will be taken from the query parameter first and if not found, from the request header.
The signature to omit file permission checks. It will be added to the URL when
retrieved through /api/db, /api/search or other endpoints which deliver
fylr URLs. The signature will be taken from the query parameter first and if
not found, from the request header.
The image information exists and is accessible. No response body.
No content
Access to the file is denied (code InsufficientRights):
the caller holds neither RIGHT_ASSET_SHOW nor
RIGHT_ASSET_DOWNLOAD (and no deep_link access applies), or
the request hash / version does not match the stored file,
or the x-fylr-signature is invalid or expired. This endpoint
returns no 401; a missing or invalid token is treated as an
anonymous request.
The addressed file id does not exist. A wrong hash, wrong
version, or an invalid / expired signature is a 403, not
a 404.
No content
GET /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{version}/info.json
GET /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{version}/info.jsonThe IIIF endpoint serves images and tiles.
Access token in the Authorization header:
Authorization: Bearer <token>.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs. The signature will be taken from the query parameter first and if not found, from the request header.
The signature to omit file permission checks. It will be added to the URL when
retrieved through /api/db, /api/search or other endpoints which deliver
fylr URLs. The signature will be taken from the query parameter first and if
not found, from the request header.
Contains the IIIF image information.
IIIF Image API 2.0 image information document — the standard
reply to a /info.json request, defined by the IIIF Image API
2.0 specification.
fylr serves this document so any IIIF-aware client (Mirador, Universal Viewer, OpenSeadragon, ...) can discover the image's dimensions, supported tile sizes and feature profile.
JSON-LD context — always the IIIF Image API 2 URL.
The image's IIIF service URL — /info.json without the
/info.json suffix.
The IIIF protocol URI.
The image's native width, in pixels.
The image's native height, in pixels.
Access to the file is denied (code InsufficientRights):
the caller holds neither RIGHT_ASSET_SHOW nor
RIGHT_ASSET_DOWNLOAD (and no deep_link access applies), or
the request hash / version does not match the stored file,
or the x-fylr-signature is invalid or expired. This endpoint
returns no 401; a missing or invalid token is treated as an
anonymous request.
The addressed file id does not exist. A wrong hash, wrong
version, or an invalid / expired signature is a 403, not
a 404.
HEAD /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{version}/info.json
HEAD /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{version}/info.jsonSame access checks as GET (and the same 403 / 404
responses; there is no 401), but returns no body on success.
Access token in the Authorization header:
Authorization: Bearer <token>.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs. The signature will be taken from the query parameter first and if not found, from the request header.
The signature to omit file permission checks. It will be added to the URL when
retrieved through /api/db, /api/search or other endpoints which deliver
fylr URLs. The signature will be taken from the query parameter first and if
not found, from the request header.
The image information exists and is accessible. No response body.
No content
Access to the file is denied (code InsufficientRights):
the caller holds neither RIGHT_ASSET_SHOW nor
RIGHT_ASSET_DOWNLOAD (and no deep_link access applies), or
the request hash / version does not match the stored file,
or the x-fylr-signature is invalid or expired. This endpoint
returns no 401; a missing or invalid token is treated as an
anonymous request.
The addressed file id does not exist. A wrong hash, wrong
version, or an invalid / expired signature is a 403, not
a 404.
No content
GET /eas/iiif/{fileId}/{hash}/{x-fylr-signature}/{version}/info.json
GET /eas/iiif/{fileId}/{hash}/{x-fylr-signature}/{version}/info.jsonThe IIIF endpoint serves images and tiles.
Access token in the Authorization header:
Authorization: Bearer <token>.
The ID of the file.
The hash is the file.hash as described here.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs.
The file.class_extension as described here.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs. The signature will be taken from the query parameter first and if not found, from the request header.
The signature to omit file permission checks. It will be added to the URL when
retrieved through /api/db, /api/search or other endpoints which deliver
fylr URLs. The signature will be taken from the query parameter first and if
not found, from the request header.
Contains the IIIF image information.
IIIF Image API 2.0 image information document — the standard
reply to a /info.json request, defined by the IIIF Image API
2.0 specification.
fylr serves this document so any IIIF-aware client (Mirador, Universal Viewer, OpenSeadragon, ...) can discover the image's dimensions, supported tile sizes and feature profile.
JSON-LD context — always the IIIF Image API 2 URL.
The image's IIIF service URL — /info.json without the
/info.json suffix.
The IIIF protocol URI.
The image's native width, in pixels.
The image's native height, in pixels.
Access to the file is denied (code InsufficientRights):
the caller holds neither RIGHT_ASSET_SHOW nor
RIGHT_ASSET_DOWNLOAD (and no deep_link access applies), or
the request hash / version does not match the stored file,
or the x-fylr-signature is invalid or expired. This endpoint
returns no 401; a missing or invalid token is treated as an
anonymous request.
The addressed file id does not exist. A wrong hash, wrong
version, or an invalid / expired signature is a 403, not
a 404.
HEAD /eas/iiif/{fileId}/{hash}/{x-fylr-signature}/{version}/info.json
HEAD /eas/iiif/{fileId}/{hash}/{x-fylr-signature}/{version}/info.jsonSame access checks as GET (and the same 403 / 404
responses; there is no 401), but returns no body on success.
Access token in the Authorization header:
Authorization: Bearer <token>.
The ID of the file.
The hash is the file.hash as described here.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs.
The file.class_extension as described here.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs. The signature will be taken from the query parameter first and if not found, from the request header.
The signature to omit file permission checks. It will be added to the URL when
retrieved through /api/db, /api/search or other endpoints which deliver
fylr URLs. The signature will be taken from the query parameter first and if
not found, from the request header.
The image information exists and is accessible. No response body.
No content
Access to the file is denied (code InsufficientRights):
the caller holds neither RIGHT_ASSET_SHOW nor
RIGHT_ASSET_DOWNLOAD (and no deep_link access applies), or
the request hash / version does not match the stored file,
or the x-fylr-signature is invalid or expired. This endpoint
returns no 401; a missing or invalid token is treated as an
anonymous request.
The addressed file id does not exist. A wrong hash, wrong
version, or an invalid / expired signature is a 403, not
a 404.
No content
GET /eas/iiif/{fileId}/{hash}/{version}/info.json
GET /eas/iiif/{fileId}/{hash}/{version}/info.jsonThe IIIF endpoint serves images and tiles.
Access token in the Authorization header:
Authorization: Bearer <token>.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs. The signature will be taken from the query parameter first and if not found, from the request header.
The signature to omit file permission checks. It will be added to the URL when
retrieved through /api/db, /api/search or other endpoints which deliver
fylr URLs. The signature will be taken from the query parameter first and if
not found, from the request header.
Contains the IIIF image information.
IIIF Image API 2.0 image information document — the standard
reply to a /info.json request, defined by the IIIF Image API
2.0 specification.
fylr serves this document so any IIIF-aware client (Mirador, Universal Viewer, OpenSeadragon, ...) can discover the image's dimensions, supported tile sizes and feature profile.
JSON-LD context — always the IIIF Image API 2 URL.
The image's IIIF service URL — /info.json without the
/info.json suffix.
The IIIF protocol URI.
The image's native width, in pixels.
The image's native height, in pixels.
Access to the file is denied (code InsufficientRights):
the caller holds neither RIGHT_ASSET_SHOW nor
RIGHT_ASSET_DOWNLOAD (and no deep_link access applies), or
the request hash / version does not match the stored file,
or the x-fylr-signature is invalid or expired. This endpoint
returns no 401; a missing or invalid token is treated as an
anonymous request.
The addressed file id does not exist. A wrong hash, wrong
version, or an invalid / expired signature is a 403, not
a 404.
HEAD /eas/iiif/{fileId}/{hash}/{version}/info.json
HEAD /eas/iiif/{fileId}/{hash}/{version}/info.jsonSame access checks as GET (and the same 403 / 404
responses; there is no 401), but returns no body on success.
Access token in the Authorization header:
Authorization: Bearer <token>.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs. The signature will be taken from the query parameter first and if not found, from the request header.
The signature to omit file permission checks. It will be added to the URL when
retrieved through /api/db, /api/search or other endpoints which deliver
fylr URLs. The signature will be taken from the query parameter first and if
not found, from the request header.
The image information exists and is accessible. No response body.
No content
Access to the file is denied (code InsufficientRights):
the caller holds neither RIGHT_ASSET_SHOW nor
RIGHT_ASSET_DOWNLOAD (and no deep_link access applies), or
the request hash / version does not match the stored file,
or the x-fylr-signature is invalid or expired. This endpoint
returns no 401; a missing or invalid token is treated as an
anonymous request.
The addressed file id does not exist. A wrong hash, wrong
version, or an invalid / expired signature is a 403, not
a 404.
No content
GET /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{x-fylr-signature}/{version} — Redirect to the IIIF info.json.
GET /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{x-fylr-signature}/{version} — Redirect to the IIIF info.json.A IIIF resource URL with no trailing path segment (with or without
a trailing slash) is 303-redirected to the corresponding
info.json. No access check is performed at this step; the rights
are checked on the redirected info.json request.
Access token in the Authorization header:
Authorization: Bearer <token>.
The ID of the file.
The hash is the file.hash as described here.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs.
The file.class_extension as described here.
Redirects to <this-url>/info.json via a Location header.
Redirects to <this-url>/info.json via a Location header.
No content
HEAD /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{x-fylr-signature}/{version} — Redirect to the IIIF info.json.
HEAD /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{x-fylr-signature}/{version} — Redirect to the IIIF info.json.Like GET on this redirect URL: 303-redirected to the
corresponding info.json.
Access token in the Authorization header:
Authorization: Bearer <token>.
The ID of the file.
The hash is the file.hash as described here.
The _uuid of the object the file is linked into. This is used for the permission check.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs.
The file.class_extension as described here.
Redirects to <this-url>/info.json via a Location header.
Redirects to <this-url>/info.json via a Location header.
No content
GET /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{version} — Redirect to the IIIF info.json.
GET /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{version} — Redirect to the IIIF info.json.A IIIF resource URL with no trailing path segment (with or without
a trailing slash) is 303-redirected to the corresponding
info.json. No access check is performed at this step; the rights
are checked on the redirected info.json request.
Access token in the Authorization header:
Authorization: Bearer <token>.
Redirects to <this-url>/info.json via a Location header.
Redirects to <this-url>/info.json via a Location header.
No content
HEAD /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{version} — Redirect to the IIIF info.json.
HEAD /eas/iiif/{fileId}/{hash}/obj_uuid/{obj_uuid}/{version} — Redirect to the IIIF info.json.Like GET on this redirect URL: 303-redirected to the
corresponding info.json.
Access token in the Authorization header:
Authorization: Bearer <token>.
Redirects to <this-url>/info.json via a Location header.
Redirects to <this-url>/info.json via a Location header.
No content
GET /eas/iiif/{fileId}/{hash}/{x-fylr-signature}/{version} — Redirect to the IIIF info.json.
GET /eas/iiif/{fileId}/{hash}/{x-fylr-signature}/{version} — Redirect to the IIIF info.json.A IIIF resource URL with no trailing path segment (with or without
a trailing slash) is 303-redirected to the corresponding
info.json. No access check is performed at this step; the rights
are checked on the redirected info.json request.
Access token in the Authorization header:
Authorization: Bearer <token>.
The ID of the file.
The hash is the file.hash as described here.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs.
The file.class_extension as described here.
Redirects to <this-url>/info.json via a Location header.
Redirects to <this-url>/info.json via a Location header.
No content
HEAD /eas/iiif/{fileId}/{hash}/{x-fylr-signature}/{version} — Redirect to the IIIF info.json.
HEAD /eas/iiif/{fileId}/{hash}/{x-fylr-signature}/{version} — Redirect to the IIIF info.json.Like GET on this redirect URL: 303-redirected to the
corresponding info.json.
Access token in the Authorization header:
Authorization: Bearer <token>.
The ID of the file.
The hash is the file.hash as described here.
The signature to omit file permission checks. It will be added to the URL when retrieved through /api/db, /api/search or other endpoints which deliver fylr URLs.
The file.class_extension as described here.
Redirects to <this-url>/info.json via a Location header.
Redirects to <this-url>/info.json via a Location header.
No content
GET /eas/iiif/{fileId}/{hash}/{version} — Redirect to the IIIF info.json.
GET /eas/iiif/{fileId}/{hash}/{version} — Redirect to the IIIF info.json.A IIIF resource URL with no trailing path segment (with or without
a trailing slash) is 303-redirected to the corresponding
info.json. No access check is performed at this step; the rights
are checked on the redirected info.json request.
Access token in the Authorization header:
Authorization: Bearer <token>.
Redirects to <this-url>/info.json via a Location header.
Redirects to <this-url>/info.json via a Location header.
No content
HEAD /eas/iiif/{fileId}/{hash}/{version} — Redirect to the IIIF info.json.
HEAD /eas/iiif/{fileId}/{hash}/{version} — Redirect to the IIIF info.json.Like GET on this redirect URL: 303-redirected to the
corresponding info.json.
Access token in the Authorization header:
Authorization: Bearer <token>.
Redirects to <this-url>/info.json via a Location header.
Redirects to <this-url>/info.json via a Location header.
No content
URL templates
Last updated