Skip to content
DevLab

Your environments

Test and production are two environments with their own Engine URL, key and DevLab account. What is in each, and how to move.

On this page
  1. What changes between them
  2. Moving to production

You integrate against a test environment first and move to production later. They are separate: each has its own Engine URL, its own key and its own DevLab account.

Your environments
WhatTest environmentProduction
Engine URLIn your kit, in Your integration.In your kit for production, when Neurologyca gives it to you.
API keyOne per team and environment, in Your account.A different one: a test key does not open production.
DevLab accountIts own account and session.Another account: a session in one environment does not open the other.
MeasurementEvery standard organization has it.Not yet.
Deferred processingRecord, upload and process with Neurologyca's processing service (Preview), turned on for your organization.The same service, with your production access, when Neurologyca gives it to you.
DELETE /users/{externalId}Physical and irreversible.Physical and irreversible.

This DevLab is connected to production.

  1. Integrating into an application, to use it with people, needs a commercial agreement with Neurologyca first (Pricing). Then ask Neurologyca for your production access: a DevLab account, a key and your production kit.
  2. Change ENGINE_BASE and ENGINE_API_KEY in your backend. The rest of what differs (for example the signed-URL secret, the webhook secret and the processor URL in deferred mode) are also your backend’s environment values: see the production checklist. Your code does not change.
  3. Check them: POST /token with the new key answers 200, and a harmless read such as GET /catalog/contexts lists your organization’s contexts.
  4. Create your people again: they do not move between environments. DELETE /users/{externalId} is physical and irreversible in both, so never point a cleanup script at production by mistake.