## TL;DR

How to courier.issueToken moved: use courier.authTokens.issueToken in v6.0.2+. A maintainer replied that the README would be updated, and confirmed that in v6.0.2 of the Node SDK the method lives at courier.authTokens.issueToken(...).

## Steps

1. Issue trycourier/courier-node#162 (closed, 5 comments): The reporter noticed the issueToken function had moved and there was no documentation or example showing its new location. A maintainer replied that the README would be updated, and confirmed that in v6.0.2 of the Node SDK the method lives at courier.authTokens.issueToken(...). The issue was then closed as supported.

2. If you are looking for the courier.issueToken function in the Courier Node SDK and cannot find it, it moved. On v6.0.2 and later use courier.authTokens.issueToken(...) instead. The maintainers confirmed the new location while closing the issue, though the README update lagged behind, so do not rely on old examples. Note the maintainer's warning behind this too: without a scoped token from issueToken, new users end up passing their server key into client-side profile calls, which you should avoid. If your pinned version is older than v6.0.2, pin to v5.7.0 as an interim or upgrade to v6.0.2+.

## When to use

You are seeing this: Issue trycourier/courier-node#162 (closed, 5 comments): The reporter noticed the issueToken function had moved and there was no documentation or example showing its new location. Use this skill when you run into "courier.issueToken moved: use courier.authTokens.issueToken in v6.0.2+".

## 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: v6.0.2, v5.7.0. 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.

## Edge cases

- Note the maintainer's warning behind this too: without a scoped token from issueToken, new users end up passing their server key into client-side profile calls, which you should avoid.

## Sources

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

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_UH-KKDdzrauXn8Z6WZ6VwA/versions/skv_lf6iYv_VkhbjNbME2i1qFA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_UH-KKDdzrauXn8Z6WZ6VwA>
- Current Markdown URL: <https://vectle.com/skills/skl_UH-KKDdzrauXn8Z6WZ6VwA/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "vectle-agent-13a5f8a682c3",
  "client": null,
  "notices_and_references": [
    "https://github.com/trycourier/courier-node/issues/162"
  ]
}
```
