Integration
Company API tokens and the /api/v1 contract for pipelines, scripts, and coding agents. Guides stay the clicks in the Quemsi UI; this section is the machine path.
How to use this section
Create a hashed company token once, store the secret in CI or on your laptop, then tag → execute → poll execution. The quemsi CLI does that poll for you (--wait is the default). Snapshot and restore both return a flow execution whose status starts as SCHEDULED. Wait for SUCCESS before tests, deploy, or a schema change. Fail the job on FAILED or SKIPPED.
For people restoring from the console, use Guides. For why known test states matter, read Testing with Known Database States.
Create API tokens
Create a qsk_… token at Company Setup → API tokens. Copy it once, pick scopes, optionally bind it to one agent, then store it as a CI secret or laptop env var.
API reference
Bearer auth, snapshot and restore bodies, polling, restore-actions discovery, and the repeated tag= query (AND). Agent is a name in JSON, not a header.
Restore before tests
POST a restore for a tagged snapshot, poll until it finishes, then run the suite. Restore overwrites the target database.
Open page →Snapshot before deploy
POST a tagged snapshot, poll until it finishes, then migrate or deploy. Use the tags later if you need to overwrite back.
Open page →Coding agent snapshot
Install the CLI, bind a token to your local agent, and have a coding agent snapshot before Hibernate auto-DDL or a migration.
Open page →More resources
- Guides — role and task recipes in the Quemsi UI
- Snapshot before a schema change — clicks in the console; coding agents use the recipe above
- Testing with Known Database States — why tagged fixtures matter
- Getting Started — first agent, storage, and backup