Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Cue the extraordinary. Show-stopping experiences that raise the digital bar. Apply now for the 2023 Adobe Experience Maker Awards.

Configuring runtime in I/O


Level 2

Hi Adobe,

We have got access to I/O runtime beta and received the namespaces for our runtime instances.
By following the documentation we configured the aio CLI and were able to upload and invoke a simple action.
However I believe we are missing one step in the configuration and we never got runtime connected to our I/O console integration.

When we are trying to retrieve the integrations from our I/O sandbox instance via the aio console:list-integrations command we get the following error:
» Error: The value "null" is invalid for option "passphrase"

We could go around this by generating an access token first with the aio jwt-auth:access-token command.

After that we were able to list out the integrations but when we try to run aio console select-integration ORGID_INTID we got the following error:

» Error: Cannot retrieve integration: (404 Not Found)

Of course we replaced the ORGID_INTID with the actual values from the namespace.


This error indicates to me that our I/O console integration is not configured with Runtime. In the documentation there is a step what states:

We don't have a possibility to enable Runtime within I/O console. Shouldn't it be Adobe who enables Runtime in our Sandbox instance first ?

Thank you in advance,


0 Replies



Hello there,


Your error is expected as you've got access to I/O Runtime through custom namespaces. This doesn't give you access to I/O Runtime through the Developer Console.


We will be revisiting the way we onboarded customers and re-onboard them through the Developer Console. Expect this to be done in May, 2020.


Level 2

Hi Mihai,

Thank you for getting back.

Will you reach out to me in May or I have to follow up on this with Adobe ?




We plan to do it on our end without you having to do anything. However, if in 2 weeks you don't see anything, please ping me again here. Thank you!


Level 2
We would also like to know this. We are creating custom APIs for clients leveraging Adobe products we are selling, and would like to keep namespaces separated. As-is, we have to use packages for each client. It works, but would we would like more separation between the clients we service.


Level 2
@Mihai_Corlan still didn't get anything from Adobe. Could you please follow up on the onboarding. Thank you

The ultimate experience is back.

Join us in Vegas to build skills, learn from the world's top brands, and be inspired.

Register Now