OpenWhisk Invalid Authorization Use

I was working on integrating serverless functions with OpenWhisk, but after I set the wsk property as given in the hypi docs, where I get the response:

ok: whisk auth set. Run ‘wsk property get –auth’ to see the new value.
ok: whisk API host set to

there seems to be a problem with the authorization, as running wsk list -v gets the error

{“error”:“Invalid authorisation use: wsk property set –apihost ‘’ –auth ‘:’”,“code”:“01FAJPQE564GS2E2BMRQCMT7F4”}
error: Unable to obtain the list of entities for namespace ‘default’: Invalid authorisation use: wsk property set –apihost ‘’ –auth ‘:’ (code 01FAJPQE564GS2E2BMRQCMT7F4)

which is also present when I try to create an OpenWhisk action. Is there a solution to this?

Thank you for the help

Can you clarify for me. Are you using the store instance domain or your app instance domain?
Authorisation for the OpenWhisk CLI is with the store instance, not your individual app instances. For example for mine demo account I use this:

wsk property set --apihost '' --auth '<instance id><token>'.
Notice the domainstarts with - all store instances have this prefix. You can get yours by going to the developer hub at Hypi.Tink and copy it.

In the screenshot you can see the Authorisation card - this is the token needed - then under the Namespace credentials you want to copy the organisation namespace to use as the instance domain.

Thank you so much for the help! I was mistaken while reading the docs. The problem seems to be fixed now.

What was the mistake shkim219? (it will help us improve the doc if we know what caused the misunderstanding)

I’ve been told that we implemented support for app instances so that you don’t need to use the store instance as I explained above so any valid instance domain and token should’ve worked

I was just confused to the wording of the section “Configure OpenWhisk” under OpenWhisk CLI, where it says

Here is App Instance Domain, e.g. and <Auth_Key> is the Authorization token of that domain.

I therefore thought that it was the hypi domain of the instance instead of the store instance, which caused this error.