Skip to content
← Back to activity

Immutable solution version

Workato embedded: WK_API_KEY vs WK_API_TOKEN and the .env parameter mismatch

Version 2Sign in to save

Complete solution

Workato embedded: WK_API_KEY vs WK_API_TOKEN and the .env parameter mismatch. In Workato embedded, WK_API_TOKEN is the token used to call the Embedded APIs, while WK_API_KEY is the vendor key generated from the Workato backend when the embedding configuration is applied. Use when hitting this exact issue with Workato embedded. Not for unrelated errors or different features.

TL;DR

In Workato embedded, WKAPITOKEN is the token used to call the Embedded APIs, while WKAPIKEY is the vendor key generated from the Workato backend when the embedding configuration is applied. Keep the two distinct in your config and make sure the .env names match what the code reads, otherwise calls authenticate against the wrong credential.

Fix

  1. In Workato embedded, WKAPITOKEN is the token used to call the Embedded APIs, while WKAPIKEY is the vendor key generated from the Workato backend when the embedding configuration is applied. Expected: You get the expected result; the problem is gone.

  2. Keep the two distinct in your config and make sure the .env names match what the code reads, otherwise calls authenticate against the wrong credential. Expected: You get the expected result; the problem is gone.

When to use

  • You are setting up or using this Workato embedded feature.
  • The symptom matches: WKAPIKEY vs WKAPITOKEN and the .env parameter mismatch.

When NOT to use

  • Unrelated Workato embedded issues (different feature, different failure).
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Workato embedded.

Variant phrasings

WKAPIKEY vs WKAPITOKEN and the .env parameter mismatch

Why it happens

GitHub issue on the Workato connection-embed sample: the sample referenced the vendor API token as WKAPITOKEN in code but as WKUSERTOKEN in .env, and the two credential names were being confused.

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • If the fix does not help, capture the full error output and check the source link for updates.

Evidence

GitHub issue on the Workato connection-embed sample: the sample referenced the vendor API token as WKAPITOKEN in code but as WKUSERTOKEN in .env, and the two credential names were being confused. Resolved: In Workato embedded, WKAPITOKEN is the token used to call the Embedded APIs, while WKAPIKEY is the vendor key generated from the Workato backend when the embedding configuration is applied. Keep the two distinct in your config and make sure the .env names match what the code reads, otherwise calls authenticate against the wrong credential. Source: https://github.com/workato/connection-embed-sample/issues/9

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Q3JikyJFLZybLCl0NSr2LA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Workato embedded: WK_API_KEY vs WK_API_TOKEN and the .env parameter mismatch <span>— Vectle</span></a>