Development

Development (dev-api.neuroon.ai) is a managed environment, separate from Production, where we iterate with continuous deploys. It is the recommended environment to integrate and test before touching Production.

URLs

Resource	URL
API	https://dev-api.neuroon.ai
Dashboard	https://dev.neuroon.ai
Widget CDN	https://cdn.neuroon.ai (same CDN; change data-api-url)

How to request access

Development is not self-service. To have a Development shop and keys provisioned for you:

1. Email Support or your commercial contact with:

• Organization name.
• Stack (your stack).
• Email of the integration owner.

2. You will receive an invite to the Development Dashboard (https://dev.neuroon.ai).
3. From there you issue your own Development Shop API Key and Widget Token.

Development credentials are not the same as Production credentials. If you already operate in Production, you will create an additional pair just for Development.

Real limitations

Non-persistent data

Development is redeployed frequently. The database may be wiped or migrated at any time. Do not upload real PII or end-customer catalogs to this environment.

Variable performance

Since Development receives continuous deploys, latencies may spike temporarily during a rollout or a migration. Do not use Development for benchmarks.

• No SLA. It is a testing environment.
• Database snapshots are not guaranteed.
• Development API keys are invalidated if your account has been inactive for a long time.
• The CDN serves the same widget version as Production. To test pre-release versions, pin widget@<version>/widget.js with the version we provide.

Recommended flow

1. Request DEV access -> receive Dashboard invite
2. Provision DEV Shop with synthetic data (10-50 products)
3. Generate DEV sk_* and DEV Widget Token
4. Point your integration to https://dev-api.neuroon.ai with those keys
5. Validate: sync, search, suggestions, tracking, conversion
6. Repeat against Production with PROD sk_*

Suggested environment variables

Only 3 variables per environment — the long-lived ones: API base URL, shop ID, and the Shop API Key (server-only):

# Development
NEUROON_API_URL=https://api.neuroon.ai
NEUROON_SHOP_ID=shop_dev_xxxxx
NEUROON_API_KEY=sk_dev_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

# Production
NEUROON_API_URL_PROD=https://api.neuroon.ai
NEUROON_SHOP_ID_PROD=shop_xxxxx
NEUROON_API_KEY_PROD=sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

What about the Widget Token? It does NOT belong here

The Widget Token lives 24 h. It is not an env var: your server signs it locally with the Shop API Key (HMAC), caches it with a margin (~23 h), and injects it into the HTML at render time, into the data-token attribute of the widget <script>. If you cache it as an env var, your integration breaks on its own in less than a day. Full pattern at Widget Token and Recipe · Server-to-server token.

"Try It" in the documentation

The "Try It" playground for API endpoints is configured by default against Development. If you want to test an endpoint without affecting your Production, just paste a Development sk_*.

Further reading

• Production
• Switching environments
• Support — to request access.