Authenticate calls from auth0 hooks to my server

[app.charttt]

I want to call my server from postRegistration hook.
I can write my own authentication layer for that, but I guess there’s already something that I can use.
The hook function looks like this: function (user, context, cb)

Looking at the context object, I’ve found that all of the following contain the same secret:
context.webtask.data.auth0-extension-secret
context.webtask.headers.authorization
context.webtask.meta.auth0-extension-secret
context.webtask.secrets.auth0-extension-secret

And all of the following contain the same jwt:
context.webtask.headers.x-wt-token
context.webtask.storage.backchannel.requestDefaults.headers.authorization
context.webtask.storage.backchannel.token
context.webtask.storage.token

I’m not even sure what fields from the context am I supposed to be using. Most of it looks like details of the request between auth0 and webtask.io (the service that auth0 are using to run my hook script)

So - can I use the secret or JWT as authentication to my own server? If I can, which path in the context should I prefer?

Thanks

[dan.woda]

Welcome to the Community @app.charttt!

To make the call between your hook and server, you should be using a M2M flow. Check out this FAQ about making the call from a rule, it is a very similar scenario:

How do I call my API from a rule?

Question: How do I call my API from a rule? Answer: To do this, you will need to configure your rule to make an API call. You can add Machine 2 Machine (M2M) authorization between your the rule and the your target API, just like you would between any two non-interactive clients, protecting the transaction with Auth0. First, register your API. This can be done via the Dashboard or the Management API. In the Dashboard, navigate to APIs → + Create API. Here you can set up your API, register you…