How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
EPCOR

EPCOR Boundaries API

Municipal boundary reference layers.

Documentation Provider Profile APIs.io OpenAPI GitHub

EPCOR Boundaries API is one of 8 APIs that EPCOR publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Boundaries. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 3 operations across 3 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 12.

Requests are made against a single base URL, https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services.

3 operations 3 paths 8 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
12
Base URL
https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
Contact
EPCOR
Resource Areas
1

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

boundaries 3

Municipal boundary reference layers.

GET
/CityBoundary_prod/FeatureServer
Get CityBoundaryprod service metadata
getCityBoundaryProdService 1 param → 200
GET
/CityBoundary_prod/FeatureServer/0
Get CityBoundaryprod layer 0 metadata
getCityBoundaryProdLayer 1 param → 200
GET
/CityBoundary_prod/FeatureServer/0/query
Query CityBoundaryprod
queryCityBoundaryProd 14 params → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are LayerMetadata (9 properties), CityBoundaryProdL0FeatureSet (7 properties), CityBoundaryProdL0Attributes (7 properties), ServiceMetadata (6 properties). Each schema is shown below with its type and property counts.

SpatialReference
object
2 properties
LayerMetadata
object
ArcGIS feature layer metadata document: field definitions, geometry type, extent, capabilities and edit timestamps.
9 properties
CityBoundaryProdL0Attributes
object
Attributes of a feature in the CityBoundaryprod layer (CityBoundaryprod, layer 0). Geometry type esriGeometryPolyline.
7 properties
GeoJSONFeatureCollection
object
RFC 7946 FeatureCollection returned when f=geojson.
3 properties
FieldDefinition
object
5 properties
CityBoundaryProdL0FeatureSet
object
Esri FeatureSet returned by a query against the CityBoundaryprod layer.
7 properties
EsriError
object
ArcGIS REST error envelope. Note that these services return HTTP 200 with this body rather than a 4xx status code.
1 property 1 required
ServiceMetadata
object
ArcGIS feature service metadata document.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

epcor-boundaries-api-openapi.yml Raw ↑

Other APIs EPCOR publishes across the network.

EPCOR Ontario Green Button (Download My Data / Connect My Data)
AE Profile APIs.io
EPCOR Catalog API
AE Profile APIs.io
EPCOR Infrastructure API
AE Profile APIs.io
EPCOR Power Outages API
AE Profile APIs.io
EPCOR Service Areas API
AE Profile APIs.io
EPCOR Us Water Outages API
AE Profile APIs.io
EPCOR Water Outages API
AE Profile APIs.io
#Boundaries
← Back to E APIs
API Details
ID
epcor:epcor-boundaries-api
Base URL
https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
Docs
https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
Provider
EPCOR
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=epcor-boundaries-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/epcor-boundaries-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of EPCOR Boundaries API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.