Skip to main content
All integrations start from a configuration profile. The SDK validates the profile before any network traffic leaves the device — invalid config fails fast with InvalidConfig instead of half-working at runtime.

Config schema

Config schema version 1. The profile is a TOML file (or an equivalent programmatic object) with these sections and defaults:

Loading configuration

The encoder is frame-based, UTF-8, and version-aware. Foreign or future-config version tags causes the loader to return a MismatchedVersion error instead of mis-reading fields.

Validation modes

MusterBoxSDK enforces different validation strictness depending on the lifecycle stage: Config secrets and credentials are never logged: diagnostics redact base_url, tokens, and key material.

Overriding the backend URL

For local development against a custom backend:
An override that is neither http:// nor https:// is rejected by validation.

Precedence

  1. Explicit base_url_override (when provided).
  2. The environment’s default base URL:
  3. The auth API base is always derived as control plane base + /api/v1.
Next: Initialization & lifecycle.
Last modified on September 10, 2026