All documentation
Authentication

Configuration, Keys and Environment Variables

Configure PulseGrid safely with environment variables, project keys and optional project ID inference.

Multi-language

Overview

Every trusted PulseGrid server integration uses a public key and secret key created for a project. SDK 0.2.0 can infer the project ID from the authenticated key when PULSEGRID_PROJECT_ID is omitted. Supplying the project ID explicitly is still useful for configuration clarity. The public key identifies the API key. The secret key authenticates trusted operations. Both should be treated as server configuration; the secret must never be exposed to browser or mobile code.

Setup

Recommended environment variables: PULSEGRID_PUBLIC_KEY=pk_... PULSEGRID_SECRET_KEY=sk_... PULSEGRID_PROJECT_ID=your-project-uuid Optional: PULSEGRID_BASE_URL=https://www.altrancconnect.com PULSEGRID_TIMEOUT=30000 JavaScript can also use ALTRANC_CONNECT_* aliases supported by SDK 0.2.0. For local development, keep secrets in a .env file that is excluded from source control. In production, use the host's environment/secrets system.

Code example

Configuration, Keys and Environment Variables
Node.js - values are read from process.env automatically 
import { createPulseGrid } from "pulsegrid";

const pg = createPulseGrid();
console.log(await pg.auth.test());

Notes

A copied key must match exactly. A single missing or changed character produces authentication failure. Rotate a key if its secret is exposed. Do not place secret keys in frontend bundles, mobile apps, screenshots, public issue trackers or public repositories.