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 update Hook Secrets added to any given Hook using the Dashboard or . Hook Secrets may also be imported and exported using the Deploy Command-Line Interface (CLI) tool. To learn more, read Deploy CLI Tool.

​
Update Hook Secrets using the Dashboard

  1. Go to Auth0 Dashboard > Auth Pipeline > Hooks and and click the pencil icon next to the Hook you want to edit.
  2. In the Hook editor, click the wrench icon and click Secrets.
  3. Click the pencil and paper icon next to the value of the Hook Secret you want to edit.
  4. Make your changes to the name and/or value of the selected Hook Secret, and click Save.

​
Update Hook Secrets using the Management API

Make a PATCH call to the Update Hook Secrets 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/secrets' \
  --header 'authorization: Bearer MGMT_API_ACCESS_TOKEN' \
  --header 'cache-control: no-cache' \
  --header 'content-type: application/json' \
  --data '{ [ "HOOK_SECRET_KEY", "HOOK_SECRET_VALUE" ], [ "HOOK_SECRET_KEY", "HOOK_SECRET_VALUE" ] }'
ValueDescription
MGMT_API_ACCESS_TOKENAccess Tokens for the Management API with the update:hooks. To learn more, read Management API Access Tokens.
HOOK_IDID of the hook for which you would like to update secrets.
HOOK_SECRET_KEYName of the secret that you would like to update for the specified hook. This endpoint accepts an object of key-value pairs.
HOOK_SECRET_VALUEValue of the secret that you would like to update for the specified hook. This endpoint accepts an object of key-value pairs.
When retrieving Hook Secrets configured for a specified Hook, values will contain the placeholder text: _VALUE_NOT_SHOWN. Be careful not to return this placeholder text during an update, or the secret’s actual value will be overwritten.

​
Learn more