API Status

Integration tests run weekly against live government APIs to verify our Zod schemas match the production response structures.

@varve/ons-api

Operational

Checked 6d ago•38/38 tests•Logs

Search API

7/7

Data API

4/4

Code Lists API

7/7

Datasets API

9/9

Observations API

2/2

Filters API

3/3

Topics API

5/5

Error Handling

1/1

@varve/statcan-wds

Failing

Checked 6d ago•15/16 tests•Logs

getChangedSeriesList

1/1

getChangedCubeList

1/1

getCubeMetadata

1/1

getSeriesInfoFromCubePidCoord

1/1

getSeriesInfoFromVector

1/1

getAllCubesList

1/1

getAllCubesListLite

1/1

getChangedSeriesDataFromCubePidCoord

1/1

getChangedSeriesDataFromVector

1/1

getDataFromCubePidCoordAndLatestNPeriods

1/1

getDataFromVectorsAndLatestNPeriods

1/1

getBulkVectorDataByRange

0/1

getDataFromVectorByReferencePeriodRange

1/1

getFullTableDownloadCSV

1/1

getFullTableDownloadSDMX

1/1

getCodeSets

1/1

@varve/statcan-rdaas

Operational

Checked 6d ago•12/12 tests•Logs

searchClassifications

1/1

getClassificationSearchFilters

1/1

searchConcordances

1/1

getConcordanceSearchFilters

1/1

getClassification

1/1

getClassificationCategories

1/1

getClassificationCategoriesDetailed

1/1

getClassificationExclusions

1/1

getTermExclusion

1/1

getClassificationIndexes

1/1

getClassificationIndex

1/1

getConcordance

1/1

@varve/worldbank-api

Operational

Checked 1d ago•7/7 tests•Logs

Catalogue API

5/5

Data API

2/2

@varve/cmhc-api

Operational

Checked 1d ago•4/4 tests

Catalogue API

2/2

Export API

2/2

Validation methodology

Status data is generated by scheduled GitHub Actions workflows. Integration tests execute weekly against live agency endpoints, validating production responses against local Zod schemas. Schema mismatches (e.g., undocumented upstream payload changes) will immediately register as test failures on this dashboard.