Overview
The IAS (Identity Assurance Services) Video Service exposes public endpoints that provide service configuration to the BCSC mobile app. These endpoints are unauthenticated and return non-sensitive operational data.
Purpose
Section titled “Purpose”The BCSC mobile app calls these endpoints to determine:
- Available destinations - which queues/destinations are active and their priority
- Service hours - when the video verification service is available (timezone, days, holidays)
This allows the mobile app to display appropriate messaging to citizens outside of service hours and route them to the correct destination queue.
Relationship to MaxConf API
Section titled “Relationship to MaxConf API”These endpoints are served by the IAS application (maintained by the Government of BC), not by the MaxConf API. They are documented here because:
- The BCSC app uses both the IAS Video Service and MaxConf API together during a video verification session
- Maximus teams occasionally need to understand the full request flow from the citizen’s perspective
graph LR
BCSC[BCSC Mobile App] -->|Service hours / destinations| IAS[IAS Video Service]
BCSC -->|POST /room/create| MaxConf[MaxConf API]
BCSC -->|WebRTC join| Pexip[Pexip Conference Node]
Base URL
Section titled “Base URL”The IAS Video Service base URL varies by IAS environment (DEV, SIT, QA, PREPROD, Production). These are managed by the Government of BC and are not directly controlled by Maximus.
IP-based field restriction
Section titled “IP-based field restriction”Some response fields are restricted based on client IP address. If the client IP is within one of the configured UST.BYPASS_IP_RANGES, all fields are returned. Otherwise, IP-restricted fields are omitted from responses.