Electricity pricing varies by location due to different grid operators, market regions, and regulatory frameworks. The Prezio API uses precise location data to determine applicable tariffs.

​
Specifying Location

Country code is ALWAYS required for all location-based requests, regardless of whether you use an address or coordinates.

Country Code (Required)

Location Data in Responses

API responses include the location data used for the request, allowing you to verify correct interpretation:
{
  "context": {
    "location": {
      "input_address": "Rådhuspladsen 1, Copenhagen",
      "coordinates": {
        "latitude": 55.6761,
        "longitude": 12.5683,
        "confidence": 9
      }
    }
  }
  // Other response data...
}
  • input_address: The address you provided (if applicable)
  • coordinates: The exact coordinates used to determine pricing
  • confidence: Geocoding confidence score (1-10, with 10 being highest)
Never provide both address and coordinates in the same request. Choose one method to specify location.

​
How Location Affects Pricing

Grid Operator

Your location determines which DSO (Distribution System Operator) serves your area, affecting grid costs.

Regional Tariffs

Organizations may have different tariffs for different geographic regions within the same country.

Local Taxes

Some electricity taxes and fees vary by municipality or region.

​
Example Requests

GET /tariffs/?country=DK&address=Rådhuspladsen 1, Copenhagen
Returns tariffs applicable to the specified address in Denmark.

​
Location Best Practices

Use Exact Locations

Provide the exact address where electricity is consumed, not approximate locations, to ensure correct tariff assignment.

Handle Geocoding Errors

Implement error handling for cases where addresses cannot be geocoded or return low confidence scores.

Verify Country Codes

Double-check that you’re using the correct country code for your location to avoid empty results.

Check Data Availability

Not all locations have data in the sandbox environment. Review our data availability guide for testing.
For most reliable results in production applications, we recommend caching the mapping between addresses and DSO service areas after initial lookups.