Developers
Core concepts

Workspaces and tenancy

Understand how FluxDigest scopes credentials, resources, and usage.

A workspace is the isolation boundary for every FluxDigest resource. API keys, subscribers, newsletters, campaigns, templates, integrations, limits, events, and audit entries belong to exactly one workspace.

Workspace-scoped routes contain the workspace ID:

/v1/workspaces/{workspace_id}/subscribers

Even though the credential is already bound to a workspace, the path remains explicit. This makes logs, copied requests, SDK calls, and future OAuth grants unambiguous.

Find a workspace ID

Use the dashboard workspace switcher or list accessible workspaces:

const workspaces = await fluxdigest.workspaces.list();

Treat IDs as opaque strings. Do not infer creation time, region, ownership, or resource type from their contents.

Isolation behavior

When a resource does not belong to the workspace in the path, FluxDigest returns 404 resource_not_found. It does not reveal whether the identifier exists in another workspace.