qibb now supports extended embedded API authentication

Simplify API workflows with fewer nodes and faster setup

‍

Authentication should be seamless, not an extra workflow step.

‍

With this update, qibb expands the authentication capabilities of the OpenAPI Client Node. You can now configure credential-based token authentication directly inside the API node, supporting APIs that authenticate via user credentials and issue a token (such as a JWT).

This includes support for credential-based token-issuing APIs as well as OAuth 2.0 ROPC, alongside existing API Key, Basic Auth, and Bearer Token methods.

The result: faster setup, fewer nodes, and cleaner API workflows; especially when working with APIs that previously required separate authentication steps.

‍

What this enables

‍

With extended embedded authentication, teams can now:

• build API workflows with fewer nodes
• configure integrations faster with less wiring and setup
• reduce workflow complexity and improve readability
• lower the risk of authentication misconfiguration
• simplify long-term maintenance across environments.

‍

• build workflows with fewer nodes, reducing complexity and keeping flows easier to read
• set up integrations faster, with authentication configured directly in the OpenAPI Client Node
• simplify long-term maintenance across environments, by avoiding duplicated authentication logic across workflows
• reduce workflow complexity and improve readability
• lower the risk of misconfiguration, by keeping authentication and API execution in one place

‍

Available across a growing list of integrations

‍

This update improves authentication handling across a wide range of API nodes, including:

Sony CI Media Cloud, Avid MediaCentral Cloud, iconik, Egnyte, OpenText Content Metadata Service, Telestream DIVA, MASV, Limecraft, Cuttingroom, Mediagenix WHATSON, Tenovos, Vidicore, Ateme Plus, Tableau, Woody IN2IT, Hiscale FLICS, DataIntell, and Leostream, with additional integrations continuing to be supported over time.

‍

🎬 See it in action

‍

 Watch how embedded authentication simplifies a real-world API workflow. In this example using Sony CI Media Cloud, authentication is configured directly in the OpenAPI Client Node, resulting in a cleaner, more compact flow without changing the workflow outcome.

‍

If you’d like to learn more or want help applying this to one of your API integrations, feel free to reach out. Book a demo here

‍

‍