Skip to main content
tempera

Provisioned private-preview workspace required

Run a browser session in staging

Use the private Tempo client configuration from onboarding to open one bounded staging workflow. This call does not create or correlate a Palette trace.

Expected outcome

A Tempo session opens the agreed staging URL and returns its session record. If onboarding configured a Palette correlation for this evaluation, your team checks that reference against the separate Palette record.

Tempera is in private preview and provides private APIs across its product areas. Access is arranged through onboarding for an agreed evaluation, with product-specific credentials, endpoints, and environment details supplied directly to your team. API maturity ranges from preview to research, and no shared cross-product endpoint is implied.

Before you start

  • Private SDK (software development kit) access supplied during onboarding
  • A staging issuer URL (the address that verifies access) and an API key stored in environment variables
  • A safe URL for the agreed test workflow

Steps

  1. 01

    Use the supplied environment

    Keep the issuer URL (the sign-in service address) and API key in your secret manager or local environment. Do not paste credentials into source code or a browser prompt.

  2. 02

    Create the canonical client

    Build the Tempera client with the authentication and staging environment values supplied during onboarding.

  3. 03

    Open one safe session

    Create a Tempo session at the approved staging URL. Start with a read-only or reversible job before enabling actions that change customer data.

  4. 04

    Check the configured correlation

    Creating a Tempo session does not prove that a Palette trace exists. If this evaluation uses both Tempo and Palette, use the integration path agreed during onboarding and separately confirm that the provisioned correlation field identifies the intended staging trace. Correlation is not automatic.

What success looks like

  • The client authenticates against the provisioned staging environment.
  • Tempo returns a session record for the approved URL.
  • When Palette is in scope, the onboarding-provisioned reference is checked against the intended Palette trace rather than inferred from the Tempo session.
  • No credential value appears in source, output, or review notes.

Canonical example

Use only after private access is ready

Open a staging session

TypeScript · private SDK surface

import { TemperaAuth, createTemperaClient } from "@tempera/sdk";

const auth = new TemperaAuth({
  issuerUrl: process.env.TEMPERA_ISSUER_URL!,
  apiKey: process.env.TEMPERA_API_KEY!,
});

const client = createTemperaClient({
  auth,
  environment: "staging",
});

const session = await client.tempo.createSession({
  url: "https://example.com/workflow",
});

This Tempo-only example opens a session. It neither creates a Palette trace nor checks a Tempo-to-Palette reference. When both products are in scope, use the workspace-specific reference field and verification step supplied during onboarding. Package access and environment values also come from onboarding.

If something is blocked

  • If authentication fails, confirm the staging issuer and credential with your Tempera onboarding contact. Do not switch to a broader credential.
  • If the URL is rejected, confirm that it is inside the workflow boundary agreed for the evaluation.
  • If no session record returns, keep the request identifier and contact the onboarding team before retrying repeatedly.