The Prospero API doesn't have versioning like many other APIs due to our rapid development process and its dual nature as our internal and external API.
As the product evolves, we need to evolve the API as well, but we take breaking changes and deprecations seriously as we know developers build applications and integrations on top of our API. If there is a breaking change in the API, we'll proactively reach out to developers that use that part of the API and give you plenty of time to make changes.
In many cases, we may mark a field in the schema or an entire endpoint as deprecated. This warning means the field or endpoint will be removed in the future, and new applications should not rely on it.
Last modified on