Protocols & Standardssince 2000⏱ ~1 min

REST

Representational State Transfer - architectural style for APIs based on HTTP and resource-oriented design.

REST (Representational State Transfer) is an architectural style for distributed systems formulated by Roy Fielding in 2000. REST uses standard HTTP methods (GET for retrieval, POST for creation, PUT/PATCH for updating, DELETE for deletion) to operate on resources identified by URLs - for example GET /meteringpoints/12345 to retrieve data about a metering pointThe fundamental unit in Elhub - the unique point in the electricity network where energy is measured and settled, identified by an 18-digit GSRN number.. REST APIs are stateless (the server does not remember the client between requests), scalable, and straightforward to integrate with from any programming language. They have become dominant in modern cloud-based integrations and are the standard for public and partner APIs in the energy sector. An important distinction: ElhubNational hub for metering data and market processes in the Norwegian electricity market. uses SOAPSimple Object Access Protocol - XML-based messaging protocol used in enterprise integrations, including Elhub./EDIFACTElectronic Data Interchange For Administration, Commerce and Transport - UN standard for electronic data exchange. (not REST), whereas modern system vendors' own APIs are typically REST. REST is the foundation for most integrations between KISCustomer Information System - the core system at power suppliers and grid companies for customer management and billing., MDMMeter Data Management - system for collection, storage, quality assurance and distribution of metering data from the electricity grid., and analytics platforms in the industry today.

IntegrationDevelopment