Changelog

For Netlify integrators and AI agents deploying to Netlify, the process of “claiming” sites allows an end user to transfer a site into their ownership. It has been a challenge for systems to know when this happens.

Today, Netlify added support for an optional claim_webhook field when generating a site claim token. This lets you receive a POST request to a specified webhook URL once a user successfully claims a site.

Why is this useful? Now, your system or AI agents can automatically react when a site changes ownership—whether that’s updating internal records, triggering notifications, adjusting billing, or syncing permissions. The webhook payload includes key details like the site ID and the new owner’s account ID, making it easier to track and integrate site claims into your workflow seamlessly.

Want to learn how to setup site claim flows? Check out this guide!

We’ve introduced built-in domain DNS verification for subdomain configuration. Previously, customers managed DNS verification themselves—now, it’s seamlessly integrated into the app, making ownership verification easier while strengthening domain protection.

We now support configuring your environment variables to apply a value to groups of branches with a given prefix. Explore the new functionality in Site configuration > Environment variables. When adding a branch value for your environment variable, add a wildcard at the end to apply the value to all branches beginning with the prefix. For example setting the branch name to release/* will apply the supplied value to branches named release/1.2, release/alpha-0.0.1, and so on.

Combine with the ability to configure your site to deploy branches matching selected prefixes to super-charge your branch workflows!

Simplify authentication and authorization for your sites and apps with the Auth0 extension. The Auth0 extension lets you connect your Netlify team and its apps to Auth0 from the Netlify Dashboard.

You can also add authorization to your functions to manage access across multiple services. For an example, check out our docs on creating a function to use Auth0 on the backend.

Learn more about our Auth0 partnership or using the Auth0 extension.

Netlify Identity and the underlying GoTrue API are now officially deprecated. This means that:

• They are still available for existing users and services.
• They will not be updated beyond major security issues.
• We will no longer fix bugs or offer troubleshooting support.

For help exporting your data to migrate, reach out to Support. We recommend using an alternative, such as the official Auth0 extension for Netlify, which simplifies authentication and authorization for your sites and apps. Learn more about setting up the Auth0 extension and why we’ve made these changes.

For an alternative to the GoTrue API, we recommend Supabase Auth, an actively maintained fork of GoTrue.

When claiming apps created by partner tools or AI code generation tools like Bolt, you’re now able to select which of your Netlify teams to claim the app into, offering greater flexibility for your workflows.

Learn how the Codezero extension for Netlify enables secure local development with internal APIs and services through Zero Environment Development, without exposing private infrastructure.

Platforms on Netlify can now deploy fullstack websites on behalf of users - complete with functions, edge functions, extensions, redirects, and more.

Sounds interesting? Get started with this developer guide.

We now support configuring your site to deploy all branches with a specific prefix. Leverage the new functionality by configuring Branch Deploys in Site Configuration > Continuous deployment. Add a wildcard at the end of your prefix to deploy all branches beginning with the given text - for example, enter release/* to automatically deploy release/alpha-1, release/v2, and so on.