The End of Life (EOL) date of Rules and Hooks will be November 18, 2026, and they are no longer available to new tenants created as of October 16, 2023. Existing tenants with active Hooks will retain Hooks product access through end of life.We highly recommend that you use Actions to extend Auth0. With Actions, you have access to rich type information, inline documentation, and public npm packages, and can connect external integrations that enhance your overall extensibility experience. To learn more about what Actions offer, read Understand How Auth0 Actions Work.To help with your migration, we offer guides that will help you migrate from Rules to Actions and migrate from Hooks to Actions. We also have a dedicated Move to Actions page that highlights feature comparisons, an Actions demo, and other resources to help you on your migration journey.To read more about the Rules and Hooks deprecation, read our blog post: Preparing for Rules and Hooks End of Life.
Because we plan to remove Rules and Hooks functions in 2026, you should create new Rules or Hooks only in your Development environment and only to test migration to Actions.To learn how to migrate your Rules to Actions, read Migrate from Rules to Actions. To learn how to migrate your Hooks to Actions, read Migrate from Hooks to Actions.
You can enable or disable hooks using the Dashboard or .
Although you may create multiple hooks for any given extensibility point, each extensibility point may have only one enabled hook at a time. Any subsequent hooks you create for that extensibility point are automatically disabled, so you must explicitly enable them. The enabled hook will be executed for all applications and APIs.
When creating new hooks, Auth0 automatically enables the first Hook you create for an extensibility point. Any subsequent hooks you create for that extensibility point are automatically disabled, so you must explicitly enable them.

​
Use the Dashboard

  1. Go to Auth0 Dashboard > Auth Pipeline > Hooks and locate the extensibility point for which you want to enable or disable a Hook.
  2. Click on the dropdown box located immediately under the extensibility point’s name and description.
    Auth0 Hook selection
  3. Select the Hook you want to enable, and confirm. If you want to disable all Hooks, select None.
A green dot will appear next to the name of any enabled Hooks.

​
Use the Management API

Make a PATCH call to the Update a Hook endpoint. Be sure to replace HOOK_ID and MGMT_API_ACCESS_TOKEN placeholder values with your Hook ID and Management API , respectively. 
curl --request PATCH \
  --url 'https://{yourDomain}/api/v2/hooks/HOOK_ID' \
  --header 'authorization: Bearer MGMT_API_ACCESS_TOKEN' \
  --header 'cache-control: no-cache' \
  --header 'content-type: application/json' \
  --data '{ "enabled": "true" }'
ValueDescription
HOOK_IDID of the hook to be updated.
MGMT_API_ACCESS_TOKENAccess Token for the Management API with the create:hooks. To learn more, read Management API Access Tokens.
The enabled property represents whether the rule is enabled (true) or disabled (false).