RidingDesk publishes two REST APIs that share the /api/v1/* URL space but are distinct products. The free Electoral Data API is open to anyone — the Canadian dataset of riding boundaries, postal-code lookups, and election results. The paid Customer Data API lets an active campaign read and write its own CRM data — voters, donations, canvassing, lawn signs.
Canadian boundaries, postal-code lookups, election results
Look up the federal, provincial, and municipal ridings for any Canadian postal code; browse boundary geometries as GeoJSON; list past elections and candidates. Free for all non-commercial use. Keys begin with ced_.
Read/write your campaign's CRM data
A scoped JSON API for the data inside an active RidingDesk campaign — voters, donations, volunteers, canvassing interactions, lawn signs, campaign metadata. Keys begin with rd_live_; available on every plan, including the free Community plan.
Add RidingDesk’s remote Model Context Protocol server as a custom connector, then sign in and choose what it may do. No key to copy:
https://ridingdesk.ca/mcp
Both APIs live under https://ridingdesk.ca/api/v1/. The path segment after /v1/ tells you which product (electoral vs the customer resources).
ced_* only works against the electoral surface. rd_live_* only works against your campaign’s CRM resources. They aren’t interchangeable.
Both APIs are vanilla JSON over HTTPS. The Customer Data API ships an OpenAPI 3.1 spec you can feed into any codegen tool.
Electoral Data API attribution: postal code coordinates from GeoNames (geonames.org), CC BY 4.0. Contains information licensed under the Open Government Licence – Canada. See data sources.