Error Model

SlaunchX errors must be read in layers.

Layer 1: Transport Status

Start with the HTTP status:

1. 401 usually means missing or invalid authentication
2. 403 usually means the request reached the gateway or policy layer but is not allowed
3. 400 usually means request shape or validation problems

Layer 2: Public Error Code

Use the response code and message to determine which contract failed.

Layer 3: Platform Context

For WEB calls, always ask:

1. was the correct portal entrypoint used
2. was the JWT session valid
3. was X-Client-Hash valid
4. was Secure Channel required

For API calls, always ask:

1. is this really an /api/v1/** endpoint
2. is the endpoint API-exposed
3. does the API key have the needed scope

Most Important 403 Lesson

403 is often a contract mismatch, not a broken endpoint.

Read Next

1. Testing and Debugging
2. the matching domain guide for your flow