> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sendora.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Resources, IDs, and workspace isolation

> The identifiers, ownership rules, and data boundaries shared by the Sendora public API.

## Opaque public IDs

IDs returned by the public API are opaque strings. Store them as strings and pass them back exactly as returned. The same id appears in the app address bar, so an id copied from the app works in the API. Do not construct ids yourself. See [Identifiers](/concepts/identifiers) for where each id comes from.

## Workspace ownership

Every API key is associated with a workspace. Authenticated public API reads and writes are scoped to that workspace. Keep workspace-specific IDs separate in multi-tenant integrations.

## Empty and missing values

Follow each endpoint schema for nullability and omission. Empty collections are valid results. Do not treat an absent optional field as an empty string unless the endpoint says so.

## Destructive operations

Delete, launch, stop, publish, rotate-secret, test-call, and outbound-message operations may have irreversible or external side effects. Require an explicit user action and log the resource ID, operation, and outcome.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.