The Openverse API is moving to api.openverse.org

Note: This change is now live after making adjustments to exclude requests from the media inserter from redirection. Earlier, this change was deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. at around 00:41 UTC on Monday June 3 but reverted at 14:00 UTC due to issues with OpenverseOpenverse Openverse is a search engine for openly-licensed media, including images and audio. Find Openverse on GitHub and at https://openverse.org. and the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor.

On 3 June 2024 the Openverse APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.’s home will be api.openverse.org and api.openverse.engineering will start redirecting to api.openverse.org. Existing API credentials and all other aspects of integrations with the Openverse API will continue to work without changes, provided requests follow redirects. Integrations that do not follow redirects will break on 3 June 2024. For the best experience, please update code referencing api.openverse.engineering to use api.openverse.org.

In order to prevent backwards compatibility issues for existing integrations (like the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ media block), we will indefinitely maintain the redirect from api.openverse.engineering, though may choose to entirely deprecate the openverse.engineering domain at some far-future date.

This change unifies Openverse’s public-facing “brand” under the openverse.org domain and removes key areas of complexity in Openverse’s infrastructure, including areas related to site reliability.

The GitHub project thread for this change and its supporting documents explain these motivations in greater detail and outlines the work we’ve completed to make this possible. To comment on or share feedback regarding this change, leave a comment on this announcement post or the GitHub project thread, or leave a message in the #openverse channel of WordPress chat.

We will soon email all registered and verified Openverse API to notify them directly of this change.