The TitlePage REST API allows developers to programmatically access bibliographic, pricing, and availability data from the TitlePage platform. This allows external systems such as websites, ecommerce platforms, and point-of-sale systems to retrieve and display book information directly from TitlePage.
Who this is for
This article is for software developers and technical teams who want to integrate TitlePage data into their own systems using the TitlePage REST API.
Overview
The TitlePage API allows external systems to retrieve book data directly from the TitlePage database. The API provides several endpoints that allow systems to perform actions such as searching for titles, retrieving detailed product records, and accessing related information including pricing, availability, and supplier data.
Responses are returned as structured JSON objects, typically including bibliographic fields such as ISBN identifiers, title and subtitle information, contributor details, publisher data, pricing, and availability indicators. The JSON structure allows developers to easily parse and integrate TitlePage data into external applications.
Use of the TitlePage REST API is subject to the API Terms of Service. Misuse may result in access being suspended or rate limits being applied. Applications should cache data where possible and avoid excessive requests. Automated systems should limit requests to no more than once every few seconds.
Accessing the API
Access to the TitlePage REST API requires authentication credentials provided by the TitlePage team. Developers must request access before they can begin using the API.
For each HTTP request, you must provide your token within the HTTP request header. The header name is Authorization and the value is Token followed by your API token.
For example:
Authorization: Token GqnjdbubqMk2ITjgx1s6DnT6OUolkjWEruia8ojSDFHUIplksdhq
Bookseller APIs
The TitlePage Bookseller APIs allow retailer systems to retrieve book metadata and supply information directly from the TitlePage database. The available endpoints and request structures are documented in the TitlePage Bookseller API Swagger documentation, which provides the full list of endpoints, required parameters, and example JSON responses.
Publisher API endpoints
The TitlePage Publisher API endpoints allow publishers and distributors to provide stock updates on single or batch product records using the ONIX partial/block update workflow. This is designed to complement rather than replace existing TitlePage ONIX update workflows.
Please note that stock/block 6 updates provided using this mechanism will be overwritten by a full ONIX record provided via SFTP. If this is not the desired outcome, the ONIX record provided by SFTP must be coded as a partial update of blocks 1–5.
Developers implementing a publisher integration should refer to the Publisher API Swagger documentation for the complete technical specification. We strongly recommend contacting the TitlePage team before beginning implementation.
TitlePage API Terms of Service
In order to use the TitlePage APIs, you agree to the following:
- Your user token may be suspended for any violation of these terms.
- Please be considerate of our servers. We recommend caching data if you expect high traffic. Automated routines should limit requests to no more than once every few seconds.
- Do not harvest or index TitlePage without our explicit written consent.
- Do not sublicense or redistribute TitlePage data to third parties without our explicit written consent.
- Do not use TitlePage data as part of a commercial product without our explicit written consent. For inquiries, please contact the TitlePage team.
- These terms may be updated or amended at any time without prior notice. Continued use of the API constitutes acceptance of the new terms. Any updates will be published on our website.
- While attribution is not required, we appreciate being mentioned where possible: "Data provided by TitlePage."
Please contact TitlePage with any questions regarding these Terms of Service.