diff --git a/src/pages/guides/using/asynchronous_calls.md b/src/pages/guides/using/asynchronous_calls.md
index 29ca713..31bed3f 100644
--- a/src/pages/guides/using/asynchronous_calls.md
+++ b/src/pages/guides/using/asynchronous_calls.md
@@ -79,8 +79,11 @@ aio rt:rule:create async-rule my-worker-trigger my-worker
 ```
 What we got so far: when our trigger is executed (my-worker-trigger), in turn will execute the action (my-worker). Here is how you can execute it. Please note the authentication header. You will need to use the same authentication as the one used by the namespace where you created these actions/trigger/rule.
 ```
-curl https://adobeioruntime.net/api/v1/namespaces/_/triggers/my-worker-trigger -X POST -H "Authorization: Basic NAMESPACE AUTHORIZATION"
+curl https://adobeioruntime.net/api/v1/namespaces/_/triggers/my-worker-trigger -X POST -H "Authorization: Basic BASE64D_API_KEY"
 ```
+
+`BASE64D_API_KEY` here is using standard Basic authentication encoding. This is generated by base64 encoding the namespace api key. For example, if your api key is `abc123`, you would base64 encode the value: `abc123`. Base64 encoding this value, would result in the encoded value: `YWJjMTIz`. Thus your `Authorization` header would be: `Authorization: Basic YWJjMTIz`.
+
 Tip: you can find the URI and the authorization for a trigger (or secured web action) by adding `-v` (verbose) to the commands to get an trigger (or action):
 ```
 aio rt:trigger:get my-worker-trigger -v