Getting Started Overview

Use this section to understand how SlaunchX integrations are structured before you open any endpoint page.

The Platform Model

SlaunchX exposes two integration chains:

1. WEB chain for browser and portal-driven experiences
2. API chain for server-to-server integrations

Those chains have different authentication, routing, and 403 behavior. Do not assume a WEB endpoint can be called like an API endpoint.

Read This Section In Order

1. Environments
2. Web Quickstart
3. API Quickstart

Then move to:

1. Web vs API Chain
2. Portal Model
3. Authentication Models
4. Error Model

The First Question To Answer

Before integrating anything, decide:

1. is this a portal or browser flow
2. is this a backend server integration
3. which business domain owns the workflow

That decision determines which docs path you should read next.

V2 Scope

The first V2 release covers these domains:

1. auth
2. account
3. workspace
4. notifications
5. wallets
6. transfers

Start from the matching domain guide once you know your chain and auth model.