Represent by Open North Getting Started: Quickstart Guide (2026)

Getting started overview

Getting started with the Represent by Open North API primarily involves understanding its core functionality for retrieving Canadian civic data. The API allows users to query for elected officials and political boundaries based on postal codes or geographic coordinates. It is designed to be accessible for non-commercial and research applications, with a straightforward process for initial integration.

The table below outlines the key steps to initiate use of the Represent by Open North API:

Create an account and get keys

For most non-commercial and research applications, Represent by Open North does not require an API key or account creation to begin making requests. The public API endpoints are generally open for direct access, simplifying the initial setup process. This approach is common among public data providers aiming to maximize accessibility for civic data initiatives, such as those that adhere to the principles of open government data.

However, if your usage involves high-volume requests, specific custom data access, or commercial applications, you may need to contact Open North directly to discuss enterprise options. Such scenarios typically involve a custom agreement and potentially dedicated API keys for rate limiting and usage tracking. Information on contacting Open North for custom pricing and enterprise use cases can be found on the Represent by Open North homepage.

To confirm whether your specific use case requires an API key or prior registration, it is recommended to consult the official Represent by Open North API documentation. This documentation provides the most up-to-date information regarding access policies and any authentication requirements.

Your first request

Making a first request to the Represent by Open North API is typically a straightforward HTTP GET operation. The primary endpoint for querying elected officials and boundaries is based on a postal code or geographic coordinates. This example demonstrates how to find elected officials for a specific Canadian postal code.

Endpoint structure

The base URL for the API is https://represent.opennorth.ca/api/.

To query for officials by postal code, the endpoint structure is:

GET https://represent.opennorth.ca/api/representatives/house_of_commons/?point={latitude},{longitude}

Or, more simply, by postal code:

GET https://represent.opennorth.ca/api/representatives/?postal_code={your_postal_code}

Example: Using a postal code

Let's use the postal code V6B 1W1 (a central Vancouver postal code) to find the federal representative. The full request URL would be:

GET https://represent.opennorth.ca/api/representatives/?postal_code=V6B%201W1

Using curl

You can execute this request from your terminal using curl:

curl "https://represent.opennorth.ca/api/representatives/?postal_code=V6B%201W1"

The API will return a JSON object containing information about the elected officials, including their names, roles, and contact details for the specified postal code. An example response might look like:

{
  "objects": [
    {
      "name": "Jenny Kwan",
      "elected_office": "MP",
      "party_name": "New Democratic Party",
      "district_name": "Vancouver East",
      "url": "https://www.ourcommons.ca/Parliamentarians/en/members/Jenny-Kwan(88812)",
      ...
    }
  ],
  "meta": {
    "limit": 20,
    "offset": 0,
    "total_count": 1
  }
}

This response structure provides metadata and an array of objects, each representing an elected official relevant to the queried postal code. For detailed explanations of all response fields, refer to the Represent by Open North developer documentation.

Common next steps

After successfully making your first request, several common next steps can help you further integrate and utilize the Represent by Open North API within your applications:

1. Explore other endpoints: The API offers various endpoints beyond just federal representatives, including provincial and municipal officials, as well as boundary data. Investigate options like /api/boundary/ to retrieve electoral district shapes or /api/representatives/provincial/ for provincial-level data. The API documentation details all available endpoints and their parameters.
2. Integrate into an application: Begin incorporating API calls into your chosen programming language (e.g., Python, JavaScript, Ruby) or framework. Most languages have HTTP client libraries that simplify making requests and parsing JSON responses. For example, in Python, libraries like requests are commonly used for this purpose.
3. Handle rate limits: While typically generous for non-commercial use, consider implementing retry logic or back-off strategies if you plan to make a large volume of requests, to gracefully handle potential rate limiting.
4. Error handling: Implement robust error handling in your application to manage cases where the API returns an error status code (e.g., 400 for bad request, 404 for not found). The API typically provides informative error messages within the JSON response.
5. Data caching: For frequently accessed data, consider implementing a caching strategy to reduce the number of API calls and improve application performance. Ensure your caching respects the dynamic nature of political data and has appropriate invalidation policies.
6. Contribute to Open North: Open North is a non-profit organization focused on civic engagement. If you find the API valuable, consider exploring ways to contribute to their mission or provide feedback on the API's utility and developer experience.

Troubleshooting the first call

When making your initial API call, you might encounter issues. Here are some common problems and their solutions:

• 404 Not Found:

  • Issue: The requested resource could not be found. This often means the URL is incorrect or the specified postal code/coordinates do not map to any known electoral district.
  • Solution: Double-check your URL against the official API documentation for endpoint paths. Verify the postal code or latitude/longitude values are valid for Canada. For postal codes, ensure correct formatting (e.g., V6B%201W1 with %20 for the space, or simply V6B1W1).

• 400 Bad Request:

  • Issue: The server cannot process the request due to invalid syntax or parameters. This can happen with malformed query parameters.
  • Solution: Review the query parameters (e.g., postal_code, point) for correct spelling and expected data types. Ensure all required parameters are present. For example, if using the point parameter, it expects a comma-separated latitude and longitude (e.g., 49.2827,-123.1207).

• No data returned (empty objects array):

  • Issue: The API call was successful (e.g., 200 OK status), but the objects array in the JSON response is empty. This usually means no officials were found for the provided query.
  • Solution: This isn't necessarily an error but indicates no matching data. Confirm the postal code or coordinates are accurate and within Canadian political boundaries. Test with a known valid postal code (e.g., K1A 0A6 for Ottawa, Ontario) to ensure the API is functioning as expected.

• Network connectivity issues:

  • Issue: Your request isn't reaching the API server at all, resulting in connection timeouts or other network errors.
  • Solution: Verify your internet connection. If you are behind a firewall or proxy, ensure it allows outgoing HTTP/HTTPS connections to https://represent.opennorth.ca.

• Incorrect API Key (if applicable):

  • Issue: If you are using an API key for an enterprise plan, an incorrect or missing key will result in authentication errors (e.g., 401 Unauthorized, 403 Forbidden).
  • Solution: Ensure your API key is correctly included in the request headers or URL parameters as specified by Open North for your specific enterprise agreement. Confirm the key is active and has the necessary permissions.

For persistent issues, reviewing the Represent by Open North documentation on error codes and common issues can provide additional context and specific guidance.