Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.prelude.so/llms.txt

Use this file to discover all available pages before exploring further.

​
Application Isolation

In the Prelude Session API, all operations are scoped and isolated at the application level. This isolation ensures that data and operations for one application cannot affect or access data from another application, providing strong security boundaries between different implementations.
To create a new application, contact us .

​
Multiple Applications

Each Prelude customer can have multiple applications, allowing you to:
  • Separate different environments (development, staging, production)
  • Isolate different products or services within your organization
  • Create dedicated applications for specific use cases

​
Application IDs

Each application is identified by a unique Application ID (appID), which serves as the namespace for all resources and operations:
  • API Endpoints: Most API paths include the appID (e.g., /v2/session/apps/{appID}/users)
  • Webhooks: Event notifications are configured per-application
  • Data Storage: All user data is partitioned by application ID

​
Benefits

  • Multi-tenancy: Manage multiple environments with complete data separation
  • Security: Prevents cross-application data access
  • Organization: Clearly separates resources between different applications
When using the Prelude Session API, you’ll need to use your assigned application ID consistently to ensure proper resource access.