Integrations, authentication, and error handling
Understand gated portal access and safe error reporting without relying on undocumented API contracts.
Authentication boundaries
Customer portal and browser-shell experiences are gated. The service uses configured identity and session controls; access can depend on account association and policy. Do not share session cookies, one-time links, or login tickets. Public docs intentionally provide no token format, API base URL, or bearer-auth recipe.
SSO status
Customer single sign-on acceptance is pending. Do not rely on SSO as an accepted or universally available sign-in path until support confirms it for your account. Use the currently provided customer portal access route.
Errors
A visible error may indicate authorization, validation, service availability, or reconciliation state. Preserve the error code/message and approximate time, then report it through support. Avoid retrying consequential operations repeatedly; an unresolved operation may require operator review. Never infer undocumented endpoints from browser traffic or source code.