11.4.0 (2024-04-16)

This release adds additional fields and links to the title metadata response.

Other changes

  • /v2/titles/:bookshareId : GET includes new fields and links:

    • lexileCode

    • lexileNumber

    • link "titleSource" for Collection Assistant users only

    • link "submitter" for Collection Assistant users only

11.3.0 (2024-03-26)

This release adds accessibility metadata by format to the "Get title metadata" endpoint.

Other changes

  • /v2/titles/:bookshareId : GET includes new listing of the following accessibility metadata response fields per format:

    • accessibilitySummary

    • accessibilityCertifications

    • accessibilityConformances

    • accessibilityFeatures

    • accessibilityHazards

    • accessModes

    • accessModesSufficient

These values are currently read only and populated as we receive new metadata from OPF or ONIX files.

11.2.0 (2024-03-05)

This release deprecates two address prefixes, "/mylists" and "/myaccount" and replaces them with camel-cased addresses consistent with others.

Deprecations and Breaking changes

  • The "/v2/myaccount" and "/v2/mylists" endpoint prefixes are deprecated. The new endpoint addresses start with "/v2/myAccount" and "/v2/myLists", using camel-casing as other endpoints do. There is not a defined end-of-life yet for the deprecated endpoints. The API documentation now refers to the new names.

    • /v2/myaccount is now /v2/myAccount

    • /v2/myaccount/history is now /v2/myAccount/history

    • /v2/myaccount/preferences is now /v2/myAccount/preferences

    • /v2/myaccount/recommendationProfile is now /v2/myAccount/recommendationProfile

    • /v2/mylists is now /v2/myLists

    • /v2/mylists/:readingListId/subscription is now /v2/myLists/:readingListId/subscription

10.13.0 (2023-11-14)

This release adds a sunset date for the Bookshare API V1.

Deprecations and Breaking changes

The Bookshare API V1 will be sunset on June 30, 2024 and will no longer be available. Partners will need to migrate to API V2 to continue accessing the Bookshare collection after that date.

10.7.0 (2023-06-20)

This release updates our authentication documentation with a guide for mobile developers on how to use OAuth2 in mobile applications.

Other changes

  • Updated the authentication documentation to include an OAuth guide for mobile developers.

10.2.0 (2023-03-07)

This release adds a new endpoint to create, store, update, and delete highlights. The release also updates the API docs for the GET /myBookmarks endpoint to include the "start" and "limit" parameters.

New endpoints

  • /v2/myHighlights : POST to store a highlight in a title of a given format.

  • /v2/myHighlights : GET to retrieve highlights in a title of a given format.

  • /v2/myHighlights : DELETE to delete a highlight in a title of a given format.

  • /v2/myHighlights : PUT to update a highlight in a title of a given format.

Other changes

  • /v2/myBookmarks : GET API docs updated to include the "start" and "limit" parameters.

10.0.0 (2023-01-24)

This release adds a new speed parameter to the "Download a title file resource" endpoint. This parameter only applies to MP3 files and dictates the playback speed of the file.

Other changes

  • "Download a title file resource" added param 'speed'. This can be used to control the playback speed of MP3 files.

  • Password length is clarified to include the maximum length allowed.

9.12.0 (2022-10-18)

This release adds a new parameter and response field to user preference endpoints to track whether or not a user wants to receive personalized recommendations. It also adds the ability for a user to delete bookmarks that they have created.

New endpoints

  • /v2/myBookmarks : DELETE to remove a bookmark from a given title.

Other changes

  • "Get my account preferences" added response field 'showRecommendations'. This can be used to determine if you want to receive personalized recommendations.

  • "Update my account preferences" added param 'showRecommendations'. This can be used to update your preference in regards to receiving personalized recommendations.

  • "Get user account preferences" added response field 'showRecommendations'. This can be used to determine if a user wants to receive personalized recommendations.

  • "Update user account preferences" added param 'showRecommendations'. This can be used to update a user’s preference in regards to receiving personalized recommendations.

9.10.0 (2022-08-30)

This release adds a new operation to support retrieving bookmarks and getting personalized book recommendations.

New endpoints

  • /v2/myBookmarks : GET to return the bookmarks for a given title.

  • /v2/myRecommendations: GET to return personalized book recommendations.

9.9.0 (2022-08-09)

This release adds a new endpoint in order to store bookmarks.

New endpoints

  • /v2/myBookmarks : POST to store a bookmark for a given title.

9.6.0 (2022-06-07)

This release adds several field values in the "Search for titles" endpoint and a new endpoint for retrieving the titles in a given Most Popular list.

New endpoints

  • /v2/popularLists/:popularListId : GET Retrieve the most popular titles in the Most Popular list with the given id.

Other changes

  • "Search for titles" Added param 'includedBisacHeadings'. This will limit results to those titles with a BISAC heading that matches or starts with one of the values provided.

  • "Search for titles" Added param 'excludedBisacHeadings'. This will limit results to those titles with a BISAC heading that does NOT match or start with one of the values provided.

  • "Search for titles" Added param 'includedBisacCodes'. This will limit results to those titles with a BISAC code that matches exactly one of the values provided.

  • "Search for titles" Added param 'excludedBisacCodes'. This will limit results to those titles with no BISAC codes that match one of the values provided.

9.5.0 (2022-05-17)

This release adds support for retrieving Most Popular lists over the last month, the last year, and for each Bookshare category.

New endpoints

  • /v2/popularLists : GET Retrieve Most Popular lists.

9.3.0 (2022-03-29)

This release adds and fixes some field values in the "Get my reading position" and "Search for titles" endpoints.

Bug fixes

  • Reading Position "dateAdded" now has earliest recorded activity timestamp for that title.

  • BISAC code values are correctly returned in "Search for titles" endpoint.

Other changes

  • Reading Position "dateModified" has most recent activity timestamp for that title.

9.0.0 (2022-01-25)

This release adds support for retrieving a list of BISAC category codes used by the system.

New endpoints

  • /v2/bisacCodes : GET Retrieve a list of BISAC category codes that are used by the system.

8.14.0 (2021-12-09)

This release adds support for retrieving a user’s reading position for a specific title format for a title.

New endpoints

  • /v2/myReadingPosition/:bookshareId/:format : GET Retrieve reading position for a specific title format for the current user.

8.8.0 (2021-07-27)

This release adds cover image links to the reading list title resource.

Other changes

  • The reading list title resource now includes cover image links.

8.5.0 (2021-05-18)

This release adds support for searching for titles by country of origin.

Bug fixes

  • The user account resource now includes "grade".

Other changes

  • General Reference, Search for titles : GET Added param 'originCountry'. This will limit results to those that originated from the given country.

8.4.0 (2021-04-27)

This release adds support for searching for reading lists by keyword. To start with, you can search private lists or public lists (referred to as "Special Collections" on the Bookshare website).

New endpoints

  • /v2/lists : GET Retrieve a list of reading lists whose name or description matches the given keyword.

8.1.0 (2021-02-23)

This release adds additional parameters to the live title count endpoint.

Bug fixes

  • Live title count endpoint has been fixed to address issues with the count not displaying properly for some users.

Other changes

  • General Reference, Live title count : GET Added new params 'includeShared' and 'country'.

8.0.0 (2021-02-02)

This release adds support for revoking an API token and also updates the add active periodical endpoints to add support for the 'editionId' parameter.

New endpoints

  • (Auth) - /oauth/revocations : Will revoke an OAuth2 access token.

Other changes

  • General Reference, Add active periodical : POST Changed param from 'bookshareId' to 'editionId'. The 'bookshareId' param, however, will continue to be accepted in place of the 'editionId' param.

  • Membership, Add active periodical for a user : POST Changed param from 'bookshareId' to 'editionId'. The 'bookshareId' param, however, will continue to be accepted in place of the 'editionId' param.

7.14.0 (2020-12-08)

This release adds support for a new type of Marrakesh eligibility for users and titles.

Deprecations and Breaking changes

  • The 'includedContentWarnings' property of the recommendation profile is deprecated, and will be removed in a future release. Any current values for existing users have been removed.

Other changes

  • Added enum option of 'marrakeshPartner' to the proofSource parameter for the following Membership Assistant endpoints:

    • Create a user for an organization.

    • Update a proof of disability.

    • Create a proof of disability.

  • The "marrakeshPODException" property has been added to the title_metadata_detail resource.

  • Collection Management, Update book metadata : PUT will accept a new "marrakeshPODException" boolean parameter.

7.13.0 (2020-11-17)

This release adds support for submitting reading activity events.

New endpoints

  • /v2/readingEvents : POST will create reading activity events that mark different types of reading activity.

7.12.0 (2020-10-27)

This release provided some changes to active titles.

Deprecations and Breaking changes

  • The "packagingStatus" property for active titles has been deprecated, since titles will no longer be packaged when they are added to an active books or active periodicals list.

Other changes

  • The active title resource now includes a "fileResourceStatus" property to represent the readiness of the particular format chosen for an active title to be able to provide file resources.

7.11.0 (2020-10-06)

This release addressed some more minor fixes.

Deprecations and Breaking changes

  • The "Create user for organization" endpoint for Sponsors, at /v2/myOrganization/members, no longer has a "proofSource" parameter, and "disabilityType" is optional. The proof source is automatically "school verified."

Other changes

  • The "Create user for organization" endpoint for Membership Assistants, at /v2/organizations/:id/members, no longer requires "disabilityType" or "proofSource". The proofSource will default to "school verified" if it is not specified when disabilityType is provided.

7.8.0 (2020-07-28)

This release addressed some more minor fixes.

Bug fixes

  • Submit Metadata For New Title endpoint now requires the "externalFormat" parameter.

7.7.0 (2020-07-07)

This release addressed some more minor fixes.

Bug fixes

  • Get My Organization Members endpoint documentation now includes the "next" token in the response description.

  • Get My Account Downloads endpoint documentation now includes the "start" parameter in the request description, and includes a realistic "dateRequested" in the sample response structure.

  • Get Periodical Editions endpoint documentation now includes the "start" parameter in the request description.

7.6.0 (2020-06-16)

This release addressed some minor fixes.

Bug fixes

  • Filtering titles at the /v2/catalog endpoint by startUpdatedDate or endUpdatedDate will return the correct range of titles.

Other changes

  • Download history records available from /v2/myaccount/history now return the date a title was requested in addition to the date that that the packaged title was downloaded. This allows a user to see when they accessed a book, even if they have yet to actually download it.

7.5.0 (2020-05-19)

This release adds periodical management options for Collection Assistants.

New endpoints

  • /v2/periodicals/:seriesId/editions/:editionId : (Collection Assistant) DELETE will remove an edition of a periodical from the collection.

Bug fixes

  • Searching for titles with the 'externalIdentifierCode' parameter now correctly finds matching titles.

  • An incorrect value for the 'start' parameter of a search request now correctly returns a 400 status code.

Other changes

  • Editing periodical series metadata now supports more properties:

    • seriesType : string<enum>

    • countries : string[]

  • Editing periodical edition metadata now supports more properties:

    • expirationDate : date, can be set to null

7.4.0 (2020-04-28)

This release introduced only one endpoint update, but restructured the documentation to make it easier to navigate for developers with different goals. There is now a page for general API endpoints that the majority of client developers can focus on, and separate pages for specialized clients that would support administrative users.

Bug fixes

  • Title searches and catalog searches that have paged far into a large result set should no longer time out.

  • Download requests return a 429 status when there are too many requests for a single user active at a time.

Other changes

  • Catalog search (/v2/catalog) supports the "titleStatus" parameter to let you filter for just live or just withdrawn titles.

  • The reference documentation for API endpoints is split from one page into three pages:

    • General Reference: Covers the endpoints that support end users of Bookshare or partner sites, such as searching for and downloading books, or managing reading lists. This also includes the description of common features of the API, such as response codes, date formats and media types.

    • Membership Management: Covers the endpoints that support Membership Assistant users in managing user accounts in order to support end users. These endpoints should be of interest only if you are targeting the small set of specialized Membership Assistant users.

    • Collection Management: Covers the endpoints that support Collection Assistant users in managing titles in their collection. These endpoints should be of interest only if you are targeting the small set of specialized Collection Assistant users.

7.3.0 (2020-04-07)

This release worked on improving some features of the OAuth 2 flow, giving clients more security, making the authorization code flow more robust, and allowing access tokens to last for their complete lifespan.

Bug fixes

  • OAuth authorization flow preserves authorization codes during the token creation process.

  • Title search that specifies a country restriction correctly filters results to include only titles available in that country.

Other changes

  • OAuth authorization now supports client secrets. Clients without a secret are still supported, but we will be transitioning away from that for clients that are able to protect a secret, primarily those that are not in browser-based apps.

  • OAuth tokens can be used until they expire, even if a new access token is created from a refresh token. Previously, using the refresh token to get a new access token would expire the previous one.

  • Editing title metadata now supports more properties:

    • availableWorldwide : boolean

    • availableToDemo : boolean

    • comments : string

    • contentType : string <enum>

    • hasEmbeddedImageDescriptions : boolean

    • lexileCode : string

    • lexileNumber : string

    • marrakeshEligible : boolean

    • nimacRestricted : boolean

    • originCountry : string

    • productIdentifier : string

    • quality : string <enum>

    • seriesId : string

    • states : string[]

7.2.0 (2020-03-17)

This release focused on maintenance fixes for a variety of issues. No new endpoints were added.

Deprecations and Breaking changes

  • The date-related fields in resource responses have been changed to return timestamp information in GMT timezone, rather than just calendar dates. The format is the "Complete date plus hours, minutes and seconds", as described in the reference on dates. This change allows API clients to provide users with accurate event dates in their local time, such as subscription start and end dates, and download history dates. There are two date fields that were not changed:

    • Copyright date remains 'YYYY'.

    • User account birth date remains a calendar date, 'YYYY-MM-DD'.

  • Deprecated: the "status" property of the title_download resource, replaced with "packagingStatus" and "downloadStatus", to represent download requests that do not involve packaging by our system. In these cases packagingStatus is null, whereas downloadStatus always has a value.

Bug fixes

  • Active titles and active periodicals lists now include values for the "size" property. This allows users or clients to gauge the resource cost of downloading or streaming a particular title.

  • User subscriptions that are created without specifying a downloadLimit now correctly get the default download limit defined for the chosen subscription type.

  • Download requests for formats in which a title is not available now correctly return a 400 response code.

Other changes

  • Title metadata update (PUT /v2/titles/:id) supports making changes to BISAC categories, via the "bisacCategories" request parameter. Along with this, the category resource that is returned as part of the title metadata for various endpoints now includes a "code" property that contains the BISAC code value (e.g. "FIC002000"). Previously, the category resource would just describe the category name (e.g. "FICTION / Action & Adventure"). For categories that are not BISAC, the code value will be empty.

7.1.0 (2020-02-25)

This release allows Collection Assistants to submit new titles, providing as full a set of metadata as they have. A title is associated with a set of file artifacts that can be downloaded, but for this release, the initial support is for titles without a corresponding file artifact. The more common case of submitting a new title with a corresponding source file artifact will be supported in the future.

New endpoints

  • /v2/titles : (Collection Assistant) POST will submit metadata for a new title to the collection, associated with the same site as the submitter. There is a required minimal set of metadata, and a larger set of supported metadata. No file attachment is supported yet, but will be coming in the future.

Bug fixes

  • Titles that are not live in the collection (i.e. withdrawn titles, or submitted but still waiting for required metadata to be supplied) can no longer be added to reading lists.

Other changes

  • Title metadata includes values for a new 'externalFormats' parameter, representing formats not delivered by the system but meaningful for a particular site.

  • Title search supports values for the new 'externalFormats' parameter, to filter results to only those which match the values given.

  • Title metadata update (PUT /v2/titles/:id) supports parameters for a variety of different contributor types (editor, arranger, translator, etc). The values provided will overwrite any existing values on the title for the given contributor type.

7.0.0 (2020-02-04)

This release adds more capabilities for Collection Assistants, such as editing properties of a title. It also introduces support for content whose artifacts are not electronic downloads. This will allow some sites to offer content that can be represented in the collection, but delivered by other means.

Note: the versioning scheme for releases has changed from "major system change"."yearly increment"."iteration increment", to "yearly increment"."iteration increment"."patch increment". Since the previous yearly increment was "6", the new version starts with "7", giving us "7.0.0" for the first release of 2020.

Deprecations and Breaking changes

  • Deprecated: the "status" property of the active_book resource, replaced with "packagingStatus" and "downloadStatus", to allow a process status for content that is requested but never packaged by the system. In these cases packagingStatus is null, whereas downloadStatus always has a value.

  • Deprecated: the "copyright" property of title_metadata_detail and title_metadata_complete, replaced with "copyrightHolder".

  • Deprecated: the "usageRestrictionId" property of usage_restriction, replaced with "restrictionCode" to represent a human-meaningful value.

New endpoints

  • /v2/titles/:id : (Collection Assistant) PUT is now supported to update the metadata of a title. In this first release, you are able to submit changes to properties that have simple types (string, integer, boolean) and multi-valued types (languages, grades, etc). More title properties will be supported in the future.

Other changes

  • The title search endpoint has an "authorFilter" parameter that allows you to limit the results of a search to those with an exact match on the value. This is different than searching by "author", where the search will try matching using partial or fuzzy matches.

  • Membership Assistants of certain sites are able to add titles to a member’s active books list, where the title may not have an electronic artifact in the collection. These types of titles can not be "downloaded", but they will show up for a member on their active books list, and on their account history list.

5.6.16 (2020-01-14)

This release begins work to give Collection Assistants more capabilities for managing their site’s collection. To start with, they will now have the ability to see the history of processing events that took place in a title’s lifetime. Metadata editing abilities will be coming in the future.

New endpoints

  • /v2/titles/:id/history : (Collection Assistant) Retrieve the list of processing events for a given title. These can tell you when a title first arrived in the system, when different metadata values were edited, and when derived artifacts were created or changed, as well as by whom.

Bug fixes

  • The "next" link on periodical edition lists is now available, to allow paging through a set of editions.

Other changes

  • The title search endpoint has a new parameter, "excludeGlobalCollection", that can be used to limit results to only those titles that are associated with the same site as the requesting user. By default, or with this parameter set to false, search results may include titles that are freely available or that have been designated as shareable from other sites.

5.6.15 (2019-12-03)

This release focused on the support for informational and system-wide messages delivered to users. Users are able to mark their messages as read, and Membership Assistants are able to view a set of messages for a given user and expire them to make them no longer appear.

Deprecations and Breaking changes

  • The "format" parameter for title searches has been deprecated, and replaced by the "formats" parameter. This new parameter can appear multiple times to allow filtering the results by multiple formats.

New endpoints

  • /v2/myMessages : Retrieve and mark as read the messages available to the current user.

  • /v2/messages : (Membership Assistant) Create, retrieve and expire individual messages for any user account associated with the same site, or system messages for all site users.

5.6.14 (2019-11-12)

This release begins building out support for informational and system-wide messages delivered to users. These will be messages created by Membership or Collection Assistants, or by system processes, and set with a defined expiration. They are meant for brief notices about topics like the overall system or topics of note about a user’s account.

As with previous releases, this feature is restricted to clients of specific sites, and will be available to users of other sites in a future release.

This release also adds content negotiation for requests of file resources, based on the 'Accept-Encoding' header. For clients who are unable to handle gzip compression, the system will return the byte stream uncompressed if it does not find an 'Accept-Encoding: gzip' request header. Since gzip compression is a standard practice for enhancing performance and user experience on the web, it is strongly recommended that clients state their ability to handle gzip if they can.

New endpoints

  • /v2/myMessages : Retrieve a set of messages for the current user. Future support will be added to mark messages as read, and to remove them before their expiration date.

  • /v2/messages : (Membership Assistant) POST endpoint to create a new message, either directed to a single user or to all members of the site.

Bug fixes

  • Keyword search now uses the current user’s language preference to rank search results.

  • Error response message text is now correct when creating a user without an email address.

Other changes

  • File resource requests for books or periodicals now perform content negotiation to determine whether the response will be gzip compressed or not, based on the 'Accept-Encoding' request header contents. For better performance, clients should send 'Accept-Encoding: gzip' whenever possible.

5.6.12 (2019-10-01)

This release completes support for recommendation profiles, active title profiles, and delivering individual file resources. The ability to get specific file resources that make up a title’s package will allow clients to offer a reading experience that doesn’t require downloading the entire content of a book at one time.

As with the previous release, these features are restricted to clients of specific sites, and will be available to users of other sites in a future release.

New endpoints

  • /v2/accounts/:userIdentifier/lists : (Membership Assistants) Retrieve and create reading lists owned by a specific user of the same site.

  • /v2/myaccount/recommendationProfile : Retrieve and update the properties of the current user’s recommendation profile, which includes author, category and content warning settings. This complements the support for Membership Assistants that was added in 5.6.11.

Bug fixes

  • Endpoints which accept strings that contain commas no longer treat the value as multiple values, but rather a single value. For example, searching for titles in the category "Cooking, Food and Wine" will now look for titles in one category, rather than looking for categories "Cooking" and "Food and Wine".

Other changes

  • /v2/lists/:id/titles : GET, POST and DELETE support was expanded to allow Membership Assistants to view titles of, add titles to, and remove titles from, a reading list if it is owned by a member of the same site.

  • /v2/titles/:bookshareId/:format/resources : Retrieve a list of file resources that make up the artifact of the given format, akin to a manifest. This endpoint was released as a demonstration in 5.6.10, and now returns real values.

  • /v2/titles/:bookshareId/:format/resources/:resourceId : Retrieve a single file resource. This endpoint was a released as a demonstration in 5.6.10, and now returns a real value.

  • /v2/myActiveBooksProfile : Added a new property, "requestList", that can be assigned a value of any reading list which the user can view. It will represent a source of books that can be added to the users active books list when that list has space available.

  • /v2/accounts/:userIdentifier/activeBooksProfile : The same property, "requestList", is available to Membership Assistants.

5.6.11 (2019-09-10)

This release focused on supporting features that will initially be limited to users of a particular private label site: periodical subscriptions, and recommendation preferences. It includes endpoints for subscribing and unsubscribing to periodicals, as well as getting a listing of a user’s subscriptions. These are available on endpoints for individual users themselves, and endpoints for Membership Assistants to act on behalf of a member from their site.

There are also new endpoints for viewing and updating a user’s recommendation preferences, both as an individual user and as a Membership Assistant acting on a user’s behalf.

These features will be made available to users of other sites in a future release.

New endpoints

  • /v2/myPeriodicals : GET supported to retrieve the list of periodical subscriptions of the current user, and POST supported to subscribe to a periodical.

  • /v2/myPeriodicals/:seriesId : DELETE supported to unsubscribe from a periodical.

  • /v2/accounts/:userIdentifier/periodicals : (Membership Assistants) Same as /v2/myPeriodicals, but for any specified user of the same site.

  • /v2/accounts/:userIdentifier/periodicals/:seriesId : (Membership Assistants) Same as for /v2/myPeriodicals/:seriesId, but for any specified user of the same site.

  • /v2/accounts/:userIdentifier/recommendationProfile : (Membership Assistants) Retrieve and update the properties of the given user’s recommendation profile, which includes author, category and content warning settings.

  • /v2/accounts/:userIdentifier/preferences : (Membership Assistants) PUT support added to complete the support for user preferences. Users have been able to view and update their own preferences, but Membership Assistants could only view them.

  • /v2/myActiveBooksProfile : Retrieve and upate the properties of the current user’s active books profile, which includes settings for how to deliver books to the user’s active books list. This complements the support added in 5.6.10 for a Membership Assistant to perform these actions.

Bug fixes

  • The sample API calls in the reference documentation no longer have places where the "roles" property in a response has blank names, such as [ "individual", "" ].

Other changes

  • A new property, "readingAge", was added to the resource at /v2/accounts/:userIdentifier/activeBooksProfile and /v2/myActiveBooksProfile.

5.6.10 (2019-08-20)

This release worked on expanding support for Sponsors and Membership Assistants to work with member rosters. It also includes the beginning of support for active books profiles, to allow users to direct the system in its allocation of books to active books list, and a demonstration of support for access to individual title files.

New endpoints

  • /v2/accounts/:userIdentifier/activeBooksProfile : (Membership Assistants) Retrieve and update a user’s settings for the selection of books to be added to their active books list. The GET request returns a resource of three groups of properties:

    • active title settings : Whether to apply recommendations to the active books list, whether to apply a request list to the active books list, and the maximum number of books that should be added by one of these methods. Updates are available to these properties via PUT on this endpoint.

    • recommendation profile : Which authors to include or exclude, which categories to include or exclude, and which content warnings to include or exclude when searching for recommended books. Also allows setting the preferred narrator gender, and narrator type (human or TTS). Updates will be available to these properties in an upcoming release via PUT on a new endpoint.

    • user preferences : Preferred language and preferred download format. Updates are already available for these properties by a PUT request at /myaccount/preferences.

  • /v2/titles/:bookshareId/:format/resources : Retrieve a list of file resources that make up the artifact of the given format, akin to a manifest. This endpoint is currently a demonstration only, and returns a set list of files. It is slated to be completed in the near future.

  • /v2/titles/:bookshareId/:format/resources/:resourceId : Retrieve a single file resource. This endpoint is currently a demonstration only, and returns a set file. It is slated to be completed in the near future.

  • /v2/organizations/:id/members : (Membership Assistants) Retrieve an organization’s roster of members. This allows Membership Assistants to do the same thing that Sponsors could do with a GET request to /v2/myOrganization/members.

  • /v2/myOrganization/members : POST supported for Sponsors to add new members to their organization. This allows Sponsors to do the same thing that Membership Assistants could do with a POST request to /v2/organization/:id/members.

Bug fixes

  • Reference documentation updates to clarify the requesting user for "Assigned Titles" endpoints, and to have a consistent description of the "user identifier" parameter to "Membership Assistant - User Accounts" endpoints.

Other changes

  • The search results from /v2/titles have additional properties in them which were formerly only in requests for title metadata:

    • site

    • readingAgeMinimum

    • readingAgeMaximum

    • categories

5.6.9 (2019-07-30)

This release worked on gaining consistency in our handling and representing of controlled vocabularies (e.g. values allowed for format, grade, language, etc), and offering Membership Assistants support for identifying user accounts and creating organizations of varying types. It was also the start of providing person names in clearer and more useful terms (see "Other changes" below).

Deprecations and Breaking changes

  • Deprecated: Individual contributor type records in title metadata. They will be represented as elements of a "contributors" resource, as a "contributor" resource with a type.

    • authors

    • arrangers

    • composers

    • lyriscists

    • translators

  • Deprecated: brailleGrade values of "grade_1" and "grade_2" on PUT requests to /v2/myaccount/preferences are deprecated in favor of "uncontracted" and "contracted". This will make the values consistent with brailleGrade that is used in artifact metadata. The values for brailleGrade on GET requests to /v2/myaccount/preferences will now be "uncontracted" or "contracted".

  • Deprecated: grade property of "uniqueID". The new field "gradeCode" will provide a better reference for allowable values based on the ONIX standard (for US grades) and the BIC group (for UK grades).

  • Narrator type was defined as allowing the values "human" and "tts" (all lower case), when used as a title search filter, and as "Human" (initial caps) or "TTS" (all upper case) when appearing in artifact metadata. The parsing of title search parameters actually only accepted "HUMAN" or "TTS" (all caps). This has been changed to use and accept the values as lower case in both input and output.

  • Narrator gender was defined in the spec as "Male", "Female" or "Other" (initial caps) when appearing in artifact metadata. In order to be consistent with other controlled vocabulary values, the values are now lower case, "male", "female", and "otherNonBinary".

New endpoints

  • /v2/organizationTypes : (Membership Assistants) Retrieve a list of possible organization types that can be used when creating a new organization. The list will be specific to the site of the user making the request

Other changes

  • All of the contributors associated with a title will be included in an array of "contributors" in the title metadata resource.

  • Contributor names will be represented with two properties, "displayName" and "indexName", rather than the name piece properties such as they are in resources like "author" (i.e. first, middle, last, prefix, suffix). This should make it clearer what the full name display is intended to be (displayName), and what the name is sorted by in the datastore (indexName).

  • The "userAccount" resource now includes a "userIdentifier" property that can be used when needing to refer to a specific user, when acting as a Membership Assistant or Sponsor. Endpoints which accept a username as the user identifier will now also accept the "userIdentifier" string. For example, a Membership Assistant could ask for an account summary by "/v2/accounts/username@someplace.org" or by "/v2/accounts/<user identifier>".