Skip to main content

Environments

Gateway Environments

Generated runtime and ingestion contracts use /sdac/... source routes. Some APIM products publish /ai/sdac/... aliases for direct gateway clients; verify the target APIM publication before using that prefix.

EnvironmentBase URLOAuth ScopeNetwork
Developmenthttps://dev-sdac-aitools-wkhc-apim.azure-api.netUse the SDAC dev scope value from the issued credentialsVNet + Service Endpoints
Staginghttps://sdac-api-staging.azure-api.netapi://sdac-api-staging/.defaultVNet + Private Endpoints
Productionhttps://sdac-api-prod.azure-api.netapi://sdac-api/.defaultVNet + Private Endpoints

When examples use an APIM alias, treat /ai/sdac/... as the published gateway prefix and /sdac/... as the source/runtime route.

Surface Prefixes

SurfacePrefixNotes
Direct gateway API/ai/sdac/... when publishedAPIM alias with gateway auth; source route remains /sdac/...
Widget same-origin ingestion proxy/api/ingestion/sdac/...Browser-facing widget chat, feedback, validation, session, and report-info routes
Widget same-origin Mastra proxy/api/mastra/sdac/...Browser-facing widget workbook upload and analysis-status routes
Mastra runtime / ingestion service/sdac/...Upstream service paths behind APIM or widget server proxies

Health and Readiness

Operational checks are deployment-facing rather than part of the gateway business API.

EndpointSurfacePurpose
GET /healthIngestion serviceBasic liveness check
GET /readyIngestion serviceDependency readiness check
GET /api/healthWidget serverWidget liveness check

If a deployment is unavailable, direct callers should expect gateway 5xx responses, and widget callers should expect proxy failures such as 502.