Skip to main content
Hooks will reach end of life (EOL) on April 30, 2027.
  • As of October 16, 2023, Hooks are no longer available in newly created tenants.
  • As of November 18, 2024, Hooks are read-only. Active Hooks still run, and you can enable or disable them and change their configuration values and secrets. You can’t edit their code in the Dashboard, the Management API, or tools that use it, such as the Auth0 CLI, Deploy CLI, Terraform, and Agent Skills.
  • After April 30, 2027, Hooks stop running and are removed.
Use Actions to extend Auth0:
You can update Hooks using the Dashboard or . You can also import and export hooks using the Deploy Command-Line Interface (CLI) tool.
Optionally, you can add secrets (such as Twilio Keys or database connection strings) to hooks.

​
Rename hooks using the Dashboard

  1. Go to Auth0 Dashboard > Auth Pipeline > Hooks and click the gear icon next to the hook you want to rename.
  2. Click Rename.
  3. Type a new name for the Hook and click Rename.
    Auth0 Rename Hooks

​
Update hook scripts using the Dashboard

  1. Go to Auth0 Dashboard > Auth Pipeline > Hooks and click the pencil icon next to the hook you want to update.
    Auth0 Hooks select a Hook
  2. Update the hook using the Hook Editor and click the disk icon to save.
    Auth0 Hook Editor

​
Update hooks using 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.
Using the Auth0 CLI? If you haven’t already, set up and authenticate your CLI session before running this command.
The enabled property represents whether the rule is enabled (true) or disabled (false).

Handle rate limits when calling APIs from within Hooks

If you call Auth0 APIs from within a Hook’s script, you will need to handle rate limits. To do so, check the X-RateLimit-Remaining header and act appropriately when the number returned nears 0.Additionally, add logic to handle cases in which you exceed the provided rate limits and receive the 429 HTTP Status Code (Too Many Requests). In this case, if a re-try is needed, it is best to allow for a back-off to avoid going into an infinite retry loop.