Overview
This REST API provides searchable access to information about geographical names in the province of British Columbia, including name status and details about the corresponding geographic feature. Please note that you may experience issues when submitting requests to the delivery or test environment if using this [OpenAPI specification](https://github.com/bcgov/api-specs) in other API console viewers.
BC Geographical Names Web Service - REST API is an open data API from gov.bc.ca. It needs no API key. It is served over HTTPS. Its OpenAPI description documents 14 endpoints.
At a glance
- Authentication
- No auth
- HTTPS
- Yes
- CORS
- Unknown
- Category
- Open Data
- Base URL
https://apps.gov.bc.ca/pub/bcgnws- Version
- 3.x.x
- Endpoints
- 14
- OpenAPI
- Specification ↗
- Spec updated
- 2021-06-21
Make a first request
Replace the placeholders; the documentation says exactly where credentials go.
curl -X GET "https://apps.gov.bc.ca/pub/bcgnws/featureCategories" \
-H "Accept: application/json"const response = await fetch("https://apps.gov.bc.ca/pub/bcgnws/featureCategories", {
method: "GET",
headers: {
"Accept": "application/json",
},
});
const data = await response.json();
console.log(data);import requests
response = requests.request(
"GET",
"https://apps.gov.bc.ca/pub/bcgnws/featureCategories",
headers={
"Accept": "application/json",
},
timeout=30,
)
print(response.json())Endpoints
| Method | Path | What it does |
|---|---|---|
| GET | /featureCategories | Get all feature categories |
| GET | /featureClasses | Get all feature classes |
| GET | /featureTypes | Get all feature types |
| GET | /features/{featureId} | Get a feature by its featureId |
| GET | /nameAuthorities | Get all name authorities |
| GET | /names/changes | Search for names with metadata changes in a given period |
| GET | /names/decisions/recent | Search for names affected by recent naming decision |
| GET | /names/decisions/year | Search for names affected by naming decisions in a given year |
| GET | /names/inside | Search in a geographic area |
| GET | /names/near | Search near to a geographic point |
| GET | /names/notOfficial/search | Search by name, limit to unofficial names only |
| GET | /names/official/search | Search by name, limit to official names only |
| GET | /names/search | Search by name |
| GET | /names/{nameId}.{outputFormat} | Get a name by its nameId |
Questions
Does the BC Geographical Names Web Service - REST API API need an API key?
No. The BC Geographical Names Web Service - REST API API can be called without an API key or sign-up, which makes it handy for prototypes and front-end demos.
Does the BC Geographical Names Web Service - REST API API support HTTPS?
Yes, the BC Geographical Names Web Service - REST API API is served over HTTPS.
How many endpoints does the BC Geographical Names Web Service - REST API API have?
Its OpenAPI description lists 14 endpoints in version 3.x.x. All of them are shown on this page.
What are alternatives to the BC Geographical Names Web Service - REST API API?
Other Open Data APIs include Search Services, Wayback API, Wikipedia, Nasdaq Data Link, University of Oslo.
Similar open data APIs
Compare alternatives →Search Services
Open DataAPI for Internet Archive's Search-related services
Wayback API
Open DataAPI for Internet Archive's Wayback Machine
Wikipedia
Open DataMediawiki Encyclopedia
Nasdaq Data Link
Open DataThe source for financial, economic, and alternative datasets, serving investment professionals.
University of Oslo
Open DataCourses, lecture videos, detailed information for courses etc. for the University of Oslo (Norway)
Data API
Open DataServes the Clever Data API
Listed from APIs.guru (CC0).