Our collection website is accessible via a JSON API which follows the JSONAPI specification.
Open to all
Our API is open to all and we’re always interested to see the innovative ways that external users and organisations are utilising our data.
- Combining our data with external data sets and resources, either your own or other publicly available data.
- Innovative interfaces for viewing and navigating our data (Timelines, Force Directed Graphs, Image Recognition).
- Textual analysis of our object descriptions and biographies to find patterns and hidden data/terms.
- Physical means of viewing and interacting with our collection (Alexa Skills, Motion Sensors).
- Integration with other platforms; maybe you’d like to build a TwitterBot that tweets a scientific discovery or pivotal invention each day.
- Or maybe you’d like to display our objects onto a map of your city.
Do let us know what you build at firstname.lastname@example.org
We periodically host HackDays where we bring together designers, programmers and technologists to use our datasets. Our last event took place in February 2017.
Formal research projects
If you are an institution or researcher interested in using our data for a formal research project, please get in touch so we can hear your plans at: email@example.com
Using our API responsibly
While we encourage the usage of our API and it’s underlying data, we ask that all copyright requirements are closely respected.
- Data in the title, made, maker and details fields: Creative Commons Zero
- Descriptions and all other text content: Creative Commons Attribution 4.0 licence
- Imagery and photography: the licensing and copyright varies per image (please check the source.legal.rights.usage for each image).
We would also ask that requests to our API are rate limited and that you contact us at firstname.lastname@example.org before setting up any significant daily exports or harvesting, we may be able to provide you with data exports in a more performative manner.
Changes to API format
While we will endeavour to keep the format of our API backwards compatible, we can not guarantee that it will remain unchanged over time and reserve the right to modify it without prior notice.