TitlePage holds bibliographic, price and availability data for the Australian book industry. This article explains how to connect your systems to that data through the TitlePage REST API, and where to find the technical detail.
Who this is for
This article is for booksellers, publishers and distributors who want to connect their own systems to TitlePage, and for anyone deciding where to start. If you are a developer ready to begin building, go straight to Developer API Info.
What is available
TitlePage offers two web service options. All new integrations should use the RESTful web services.
- RESTful web services. Our current offering, and the option we recommend for all new integrations. REST supports single and multiple ISBN searches, detailed product records, and access to prebuilt record collections. It also allows publishers to supply more regular or live stock updates, and booksellers to supply their own stock levels so readers can locate products at their local bookshop.
- Legacy SOAP API. Our older service, which returns general information and price and availability data for a single title using an ISBN-13 search. It is now end of life and will be retired. Access is connected to your TitlePage bookseller user account.
The TitlePage APIs are available to all TitlePage booksellers.
Legacy SOAP API: important information
The TitlePage SOAP API is currently end of life and will be retired soon. All future integrations should use the modern RESTful API.
Use of the legacy SOAP web service is only recommended for existing integrations, such as one that may already be in place through your Point of Sale provider. Access to the legacy SOAP web service is connected to your TitlePage bookseller user account.
Long-term availability of the SOAP service is not guaranteed. If you have an existing SOAP integration, we recommend planning a move to the RESTful API. Contact titlepage@publishers.asn.au if you need further information.
Where to start
What you need to do depends on the systems you use, what you are trying to achieve, and the technical resources available to you.
- If you use a commercially available Point of Sale (POS) system, contact your POS provider first. They may already support a TitlePage integration, or be able to build a custom one.
- If you have your own development team or an external developer, send them to Developer API Info, which covers authentication, the available endpoints, and the API Terms of Service.
- If you are not sure which option suits you, contact us and we can talk it through before any development begins.
Access to the API requires credentials issued by the TitlePage team, so please get in touch before starting work.
Full documentation
The complete written guide covers both the RESTful web services and the legacy SOAP service, including how to use the Swagger documentation, the available endpoints, and their parameters and responses. Note that the SOAP sections are retained for reference by existing integrations only.
- TitlePage Web Services API documentation (PDF)
- Developer API Info, for authentication, endpoints and terms of use
- TitlePage Swagger documentation, for the live endpoint reference
- Prebuilt record collections, including new release files and promotional title selections
Getting help
If you have questions about which service to use, need API credentials, or want to discuss an integration, email us at titlepage@publishers.asn.au or submit a request.