Skip to main content

AI

Ask

Projects

Where projects are made and their credentials live: every project carries a Live and a Test environment, each with its own ingest key and signing secret. Rotation comes with a grace window so a deploy can catch up, and a secret is shown exactly once, at the moment it is minted.

The projects screen in the Live environment
The projects screen, Live environment.
The projects screen in the Live environment, dark theme
The projects screen, Live environment.

The grid

Each row is one project: its name, its identifier chip, which environments it carries, a masked glimpse of its ingest key and when it was made. The Active and Archived tabs split the population, the search narrows by name, and New project opens a dialog that creates the project and reveals its ingest keys once, in the dialog itself, because that is the only moment they are shown.

Renaming and archiving live on the row. Archiving asks for the project identifier to be typed back, because an archived project stops accepting traffic; the Archived tab restores.

Opening a project

A project opened to its current environment card, credentials masked
A project opened: the current environment, both credentials masked.
A project opened to its current environment card, credentials masked, dark theme
A project opened: the current environment, both credentials masked.

Selecting a row opens the project: a card for the environment the console is in, carrying both credentials labelled. Deliberately not both cards at once: showing the Test key while working in Live is a mix-up waiting to happen, so the other environment's card appears by switching environment. The ingest key is what SDKs send events with; rotating it offers a grace window (immediately, one hour, a day or a week) during which the old key still ingests, so a fleet mid-deploy does not drop events. The signing secret is what the Messenger's identity verification signs with; its action reads Create until one exists and Rotate after. Either mint prints the new value exactly once, and a replaced secret says it replaced one, so an accidental rotation is visible before it bites.

Where this meets the API

What the keys are for is the Keys guide. On the wire: the listing is the projectGroups query, creation and lifecycle are createProject, renameProject and archiveProject, and the credentials rotate through rotateProjectKey and rotateSigningSecret (GraphQL reference). The ingest key authenticates event ingestion; the signing secret backs Messenger identity verification (Messaging pillar).