> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/developers-guides/scripting/modules/obsolete-neo-names.md).

# Obsolete neostore names

Catalog of the legacy neostore names still found in scripts: which still work, which are kept on purpose, and how to migrate the neo/ module imports.

{% hint style="warning" %}
**Deprecated.** The `neo/` module names still work, but new scripts import the `twc/` modules. The obsolete endpoint key is described in [Obsolete customerProvider script key](https://docs.thewalletcrew.io/developers-guides/scripting/endpoints/customer-provider-obsolete.md).
{% endhint %}

The prefix `neostore` is the platform's former name and is kept in technical identifiers. The first script modules, `neo/secrets` and `neo/secutix`, were named after it. The modules are now published under `twc/`, the prefix of The Wallet Crew. The old names are kept so that existing scripts do not break, but new scripts, and scripts that are edited anyway, use the new names. The other technical identifiers are listed in the section Other legacy names. This page lists the correspondence and explains how to migrate.

<details>

<summary><strong>Real-world examples</strong></summary>

* A script written years ago starts with `import { getSecret } from "neo/secrets"` and keeps working; its import line is changed to `twc/secrets` the next time the file is edited.
* A review of a tenant's scripts finds `neo/` imports in several files and replaces them in one pass.

</details>

## Module names

| Obsolete name | Current name  | Exports     | Page                                                                                        |
| ------------- | ------------- | ----------- | ------------------------------------------------------------------------------------------- |
| `neo/secrets` | `twc/secrets` | `getSecret` | [twc/secrets](https://docs.thewalletcrew.io/developers-guides/scripting/modules/secrets.md) |
| `neo/secutix` | `twc/secutix` | `fetch`     | [twc/secutix](https://docs.thewalletcrew.io/developers-guides/scripting/modules/secutix.md) |

Modules added later exist only under `twc/`. In particular `twc/apple-music` has no `neo/` equivalent.

## Behavior of the obsolete module names

An import of an obsolete name resolves to exactly the same module as the current name, with the same functions and the same behavior. Nothing else changes. The only difference is a warning in the platform's log, written once per server for each platform version, tenant and module, which says that the module is obsolete and names its replacement. A script is therefore not slowed down, and the warning does not repeat on every run.

The advanced configuration editor offers the typings of the current names, and marks the obsolete names as deprecated.

## Migration

The migration is a text replacement in the `import` line of each file; the imported names stay the same.

```js
// Before
import { getSecret } from "neo/secrets";
import { fetch as secutixFetch } from "neo/secutix";

// After
import { getSecret } from "twc/secrets";
import { fetch as secutixFetch } from "twc/secutix";
```

A script that uses `neo/secutix` without an alias shadows the global `fetch` in its file, exactly as it does with `twc/secutix`, so the replacement does not change which `fetch` a file uses.

## Other legacy names

These names keep the platform's former name and must be written exactly as shown. They are not obsolete modules.

| Name                            | Where it appears                                                                                            |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| `x-neostore-signature`          | Webhook signature header                                                                                    |
| `X-NEOSTORE-EVENTNAME`          | Webhook event name header                                                                                   |
| `X-NEOSTORE-TENANTID`           | Webhook tenant header                                                                                       |
| `neo.authToken`                 | Query-string parameter that carries a login token to the holder pages                                       |
| `auth.neostore.cloud`           | Authentication host name                                                                                    |
| `app.neostore.cloud`            | Application host name                                                                                       |
| `MapToNeostore`                 | Optional handler of the Secutix contact mapper (`extensions.secutix.contact.mapper`)                        |
| `neo.*` entity keys, `neo.id`   | Account and pass data (`neo.lng`, `neo.pass.*`); at pass creation, the identifier `neo.id` sets the pass id |
| `neostore.*` Klaviyo properties | Klaviyo profile properties                                                                                  |

## Checking the result

After saving the configuration, a flow that runs the script is executed once, and the outcome is checked as before (a secret is read, a Secutix call answers). The import is resolved when the script file loads, so a typo in the new name, such as `twc/secret`, fails the load of the file and, with it, the script endpoints of the tenant.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/developers-guides/scripting/modules/obsolete-neo-names.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
