Web Quickstart

Use this path when your client is a browser, portal UI, or any user-driven flow that operates on the WEB chain.

Typical Sequence

1. enter through the correct portal host
2. establish Secure Channel if the flow requires it
3. complete login, registration, or another entry flow
4. receive a JWT session
5. send authenticated WEB requests with the expected headers

Required Concepts

Read these before using the WEB chain:

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

Required Headers In Practice

Depending on the endpoint, a valid WEB request may need:

1. Authorization: Bearer <jwt>
2. X-Client-Hash
3. X-SC-Session-Id
4. portal entrypoint context injected by the gateway

Common 403 Causes

1. the request bypassed the expected portal entrypoint
2. the token belongs to a different portal type
3. X-Client-Hash does not match the active session
4. the endpoint requires Secure Channel and the request is not in that context

Next Step

Move to the relevant domain guide:

1. Auth
2. Account
3. Workspace