Temporal Continuity API / Installation

IT installation and deployment

Install the public SDK in your existing server-side Node.js application. Temporal Continuity is a hosted API: there is no local service to deploy.

Integration reference: the public SDK has been implemented by an independent application. Validate the configuration and expected behavior in your own environment before rollout.

01 / Before installationConfirm prerequisites and ownership
  • Runtime: Node.js 18 or newer according to the SDK package requirement. For production, use your organization's supported Node LTS.
  • Package access: npm and access to your approved registry with a committed application lockfile.
  • Network: DNS and outbound HTTPS/TLS over TCP 443 to api.rscapex.com, including any organizational proxy or network policy.
  • Access: Active Temporal Continuity account, organization, project and environment, with the appropriate service entitlement.
  • Secrets: Server-side secret storage and controlled runtime injection. Never expose API keys in browser bundles or client-side code.
  • Ownership: Identify the application owner, deployment owner, credential custodian and incident contact.
02 / Developer ConsoleCreate credentials and save the environment scope

Sign in, create a test or production key and save the complete key when it is displayed. Record the matching organization, project and environment IDs. Keep test and production secrets separately managed.

Inject the following values into the server process. A local .env file is acceptable for development when excluded from source control; use a managed secret store in production.

TEMPORAL_CONTINUITY_API_KEY=<key from Developer Console>
TEMPORAL_CONTINUITY_BASE_URL=https://api.rscapex.com
TEMPORAL_CONTINUITY_ORGANIZATION_ID=<organization ID>
TEMPORAL_CONTINUITY_PROJECT_ID=<project ID>
TEMPORAL_CONTINUITY_ENVIRONMENT_ID=<environment ID>

Test keys normally begin with rms_test_; production keys with rms_live_. The credential and scope must match. Do not store secrets in tickets, commits, logs or screenshots.

03 / Existing application directoryInstall the published SDK

Open a terminal at the root of your existing Node.js application.

npm install temporal-continuity

Record and review the installed version. Commit the updated package manifest and lockfile through normal code review.

npm ls temporal-continuity
npm view temporal-continuity version engines
# In CI/CD after committing package-lock.json:
npm ci

npm ci requires a matching lockfile. Installing the SDK does not automatically configure your AI provider or connect your orchestration framework.

04 / Server-side application codeInitialize the client with your environment values

Use the official RMS SDK export (also available as TemporalContinuity). Fail startup when required configuration is absent.

import { RMS } from "temporal-continuity";

const required = [
  "TEMPORAL_CONTINUITY_API_KEY",
  "TEMPORAL_CONTINUITY_BASE_URL",
  "TEMPORAL_CONTINUITY_ORGANIZATION_ID",
  "TEMPORAL_CONTINUITY_PROJECT_ID",
  "TEMPORAL_CONTINUITY_ENVIRONMENT_ID",
];
for (const name of required) {
  if (!process.env[name]) {
    throw new Error(`Missing required configuration: ${name}`);
  }
}

export const rms = new RMS({
  apiKey: process.env.TEMPORAL_CONTINUITY_API_KEY,
  baseUrl: process.env.TEMPORAL_CONTINUITY_BASE_URL,
  organizationId: process.env.TEMPORAL_CONTINUITY_ORGANIZATION_ID,
  projectId: process.env.TEMPORAL_CONTINUITY_PROJECT_ID,
  environmentId: process.env.TEMPORAL_CONTINUITY_ENVIRONMENT_ID,
});

Connect the SDK to your existing application workflow using a supported public method. Keep existing identity and cognition-provider configuration under your application's control. Provider credentials are required only when your selected provider needs them.

05 / Deployment environmentValidate connectivity, configuration and authorization

Run these checks from the actual deployment network, not only a developer workstation:

node --version
npm ls temporal-continuity
curl -I --max-time 15 https://api.rscapex.com/

A response to curl establishes network reachability, not credential authorization. For an optional read-only SDK connectivity check, run this code in your server environment with its configured secrets:

import { RMS } from "temporal-continuity";

const rms = new RMS({
  apiKey: process.env.TEMPORAL_CONTINUITY_API_KEY,
  baseUrl: process.env.TEMPORAL_CONTINUITY_BASE_URL,
  organizationId: process.env.TEMPORAL_CONTINUITY_ORGANIZATION_ID,
  projectId: process.env.TEMPORAL_CONTINUITY_PROJECT_ID,
  environmentId: process.env.TEMPORAL_CONTINUITY_ENVIRONMENT_ID,
});

try {
  await rms.listVerification();
  console.log("Public verification endpoint reachable");
} catch (error) {
  console.error({
    status: error.status,
    code: error.body?.error?.code,
    requestId: error.body?.error?.requestId,
  });
  process.exitCode = 1;
}

Before go-live: separately validate an authorized tenant-scoped operation in your test environment and confirm your application's selected public API workflow with approved test data. The public verification endpoint is not an authenticated tenant test.

06 / Common installation failuresTroubleshooting and recovery
SymptomRecommended action
Package install failsCheck npm registry permissions, proxy, DNS and approved package access.
SDK configuration errorCheck runtime secret injection and all five required environment settings. Do not print the key.
TLS or connection failureCheck egress TCP 443, DNS, proxy and the trusted CA chain. Do not disable certificate validation.
401 / 403Check credential status and that organization, project and environment values match the issued key.
404 / 409Check resource identity or conflict before attempting the operation again.
429Observe Retry-After and use bounded backoff.
5xx / timeoutCapture sanitized status and request ID, then follow your organization's bounded retry/escalation policy.

When escalating, provide UTC time, environment, SDK version, sanitized error status/code/request ID and reproduction steps. Never share live keys, authentication headers or private application data.

07 / Production acceptanceHand off a supportable installation
  • Dependency version and lockfile reviewed; clean npm ci succeeds in your deployment pipeline.
  • Test and production credentials are stored separately with least-privilege runtime access.
  • Network/TLS checks and an authorized test-environment operation succeed.
  • Your selected application integration is verified with approved test data.
  • Logging excludes credentials and private request contents; retries handle throttling without uncontrolled duplication.
  • Assign monitoring, incident-response, credential-rotation and rollback ownership before production release.

Rolling back application code does not reverse API operations already completed. Follow your normal change-control process.

Developer API endpoints

Base URL: https://api.rscapex.com. Methods and routes below are from the published SDK interface.

MethodEndpoint
POST/v1/participants
GET/v1/participants/{id}
POST/v1/relationships
GET/v1/relationships/{id}
POST/v1/relationships/{id}/contributions
GET/v1/relationships/{id}/context
GET/v1/relationships/{id}/history
POST/api/apex/exchange
POST/api/apex/composition
POST/api/apex/artifacts/image
POST/api/apex/migrations
PATCH/api/apex/migrations
GET/api/apex/migrations
GET/v1/verification