Credentials, identifiers and resource boundaries
Resource model
A developer account owns or joins workspaces. A workspace contains databases. A database has engine credentials, users, backups, schedules and metrics. The workspace owner’s plan controls resource quotas; some features also check the acting developer’s plan.
A Redis “database” is a logical namespace on a shared Redis service. Its ACL limits keys to a prefix; it is not a dedicated Redis server or a freely selectable database number. Use database 0 from the supplied URI and the exact returned key_prefix.
Use the right credential
| Credential | Used for | Where it belongs |
|---|---|---|
| Dashboard login/session | Human account and resource management | Signed-in Lordbase browser session |
Developer access token (lb_pat_…) | Scoped management API automation | Your server-side automation secret store |
| Database username/password | Native PostgreSQL, Redis or MongoDB connections | Your application server’s secret configuration |
The management API uses Authorization: Bearer for token authentication. Do not substitute a database password or a SyAuth credential. Native drivers use database credentials and do not send Lordbase management headers.
Keep these identifiers separate
| Value | Example/shape | Meaning |
|---|---|---|
workspace_id | UUID | Workspace resource; required in editor query strings |
database_id | UUID | Resource ID in management URLs |
db_name / connection database | Generated native name | PostgreSQL database or MongoDB authentication/data database |
display_name | Human-readable label | UI label; not a connection identifier |
Database user id | UUID | User resource for management URLs |
Database username | Engine login name | Includes a generated prefix; copy exactly |
Member id | UUID | Membership record for role changes/removal |
Member user_id | Account identifier | Developer account; not the membership record ID |
Backup/schedule/token id | UUID | The corresponding management resource |
States matter
Databases can be creating, active, paused, error or deleted. Connections need an active database even though connection details are also readable while paused. List endpoints normally hide failed/deleted database records; retain any failure response ID for diagnosis.
Backup states are separate from database states. A backup creation response means a job exists; only completed indicates that job finished. It still takes a successful restore test to demonstrate recovery.