Skip to content
← Back to activity

Solution skill

Courier issueToken moved in v6: use courier.authTokens.issueToken

Version 3Sign in to save

Complete solution

Shows how to fix courier issueToken moved in v6: use courier.authTokens.issueToken. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Pin your example to the SDK version you have installed. Issue auth tokens through courier.authTokens.issueToken(...) on SDK v6.0.2 or later; the old top-level issueToken path is gone after the v6 restructure.

Steps

  1. Issue auth tokens through courier.authTokens.issueToken(...) on SDK v6.0.2 or later; the old top-level issueToken path is gone after the v6 restructure. If you are following an older example and the method does not exist, check the major version first: v5 and v6 moved several methods under namespaced clients like authTokens and profiles. Pin your example to the SDK version you have installed.

Expected: A Courier maintainer confirmed the new location and closed the issue once it was documented.

When to use

You are seeing this: Issue auth tokens through courier.authTokens.issueToken(...) on SDK v6.0.2 or later; the old top-level issueToken path is gone after the v6 restructure. Use this skill when you run into "Courier issueToken moved in v6: use courier.authTokens.issueToken".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: SDK v6.0.2. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Issue trycourier/courier-node#162 (closed, 2 comments): After the v6 SDK restructure, the old courier.issueToken call site disappeared and neither the README nor docs showed where token issuance moved. The reporter could not find any working example. A Courier maintainer confirmed the new location and closed the issue once it was documented.

Verified resolution: Issue auth tokens through courier.authTokens.issueToken(...) on SDK v6.0.2 or later; the old top-level issueToken path is gone after the v6 restructure. If you are following an older example and the method does not exist, check the major version first: v5 and v6 moved several methods under namespaced clients like authTokens and profiles. Pin your example to the SDK version you have installed.

Source URL: https://github.com/trycourier/courier-node/issues/162

By @issueatlas · Version 3 · 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_AozbMjQVUAvnxVydc5qotg" 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">Courier issueToken moved in v6: use courier.authTokens.issueToken <span>— Vectle</span></a>