Skip to main content
POST
/
meter-orders
Create a smart meter order
curl --request POST \
  --url https://api.nomos.energy/meter-orders \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "subscription": "sub_mi4f0oda6x9m7gcsvjk0ole1"
}
'
import requests

url = "https://api.nomos.energy/meter-orders"

payload = { "subscription": "sub_mi4f0oda6x9m7gcsvjk0ole1" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)
const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({subscription: 'sub_mi4f0oda6x9m7gcsvjk0ole1'})
};

fetch('https://api.nomos.energy/meter-orders', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));
<?php

$curl = curl_init();

curl_setopt_array($curl, [
CURLOPT_URL => "https://api.nomos.energy/meter-orders",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS => json_encode([
'subscription' => 'sub_mi4f0oda6x9m7gcsvjk0ole1'
]),
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>",
"Content-Type: application/json"
],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}
package main

import (
"fmt"
"strings"
"net/http"
"io"
)

func main() {

url := "https://api.nomos.energy/meter-orders"

payload := strings.NewReader("{\n \"subscription\": \"sub_mi4f0oda6x9m7gcsvjk0ole1\"\n}")

req, _ := http.NewRequest("POST", url, payload)

req.Header.Add("Authorization", "Bearer <token>")
req.Header.Add("Content-Type", "application/json")

res, _ := http.DefaultClient.Do(req)

defer res.Body.Close()
body, _ := io.ReadAll(res.Body)

fmt.Println(string(body))

}
HttpResponse<String> response = Unirest.post("https://api.nomos.energy/meter-orders")
.header("Authorization", "Bearer <token>")
.header("Content-Type", "application/json")
.body("{\n \"subscription\": \"sub_mi4f0oda6x9m7gcsvjk0ole1\"\n}")
.asString();
require 'uri'
require 'net/http'

url = URI("https://api.nomos.energy/meter-orders")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "{\n \"subscription\": \"sub_mi4f0oda6x9m7gcsvjk0ole1\"\n}"

response = http.request(request)
puts response.read_body
{
  "object": "meter_order",
  "id": "prdo_mi4f0oda6x9m7gcsvjk0ole1",
  "subscription": "sub_mi4f0oda6x9m7gcsvjk0ole1",
  "customer": "cus_mi4f0oda6x9m7gcsvjk0ole1",
  "provider": "energy-metering",
  "status": "waiting",
  "created_at": "2024-03-14T12:00:00Z",
  "updated_at": "2024-03-14T12:00:00Z"
}
{
"code": "BAD_REQUEST",
"message": "invalid_type in 'end': Required",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/BAD_REQUEST"
}
{
"code": "UNAUTHORIZED",
"message": "Invalid or malformed token",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/UNAUTHORIZED"
}
{
"code": "PAYMENT_REQUIRED",
"message": "Payment required",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/PAYMENT_REQUIRED"
}
{
"code": "FORBIDDEN",
"message": "You are not allowed to access this resource",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/FORBIDDEN"
}
{
"code": "NOT_FOUND",
"message": "Resource not found",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/NOT_FOUND"
}
{
"code": "METHOD_NOT_ALLOWED",
"message": "Method not allowed",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/METHOD_NOT_ALLOWED"
}
{
"code": "CONFLICT",
"message": "Resource already exists",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/CONFLICT"
}
{
"code": "UNPROCESSABLE_ENTITY",
"message": "invalid_enum_value in 'status': Invalid enum value. Expected 'pending' | 'active' | 'ended'",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/UNPROCESSABLE_ENTITY"
}
{
"code": "TOO_MANY_REQUESTS",
"message": "Wait 30 seconds before retrying.",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/TOO_MANY_REQUESTS"
}
{
"code": "INTERNAL_SERVER_ERROR",
"message": "Internal Server Error",
"requestId": "37a04f8f-e791-491c-81e1-86cd304649bb",
"docs": "https://docs.nomos.energy/api-references/errors/INTERNAL_SERVER_ERROR"
}

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

The meter order to create

subscription
string
required

ID of the subscription to create the meter order for

Example:

"sub_mi4f0oda6x9m7gcsvjk0ole1"

Response

The created meter order details

object
enum<string>
required

Type of the object, always 'meter_order'

Available options:
meter_order
id
string
required

Unique identifier for the meter order

Example:

"prdo_mi4f0oda6x9m7gcsvjk0ole1"

subscription
string
required

ID of the subscription

Example:

"sub_mi4f0oda6x9m7gcsvjk0ole1"

customer
string
required

ID of the customer

Example:

"cus_mi4f0oda6x9m7gcsvjk0ole1"

provider
enum<string>
required

The smart meter provider

Available options:
energy-metering,
metrify,
inexogy
Example:

"energy-metering"

status
enum<string>
required

Current status of the meter order.

Possible values:

  • waiting: The customer has requested a smart meter - waiting to transfer the order to the meter provider (e.g. missing MaLo, MeLo,..)
  • ordered: We have transferred the order to the meter provider
  • checked: The meter provider did a smart meter check and confirmed to process the order
  • installation_planning: The meter provider is planning the installation (e.g. waiting for the customer to confirm the installation date)
  • installation_scheduled: The meter provider has scheduled the installation with the customer (e.g. waiting for the customer to confirm the installation date)
  • installation_waiting: The meter provider is waiting for the installation to start (e.g. waiting for the customer to confirm the installation date)
  • installation_finished: The meter provider has finished the installation and the new meter data has been transferred to the network operator
  • activated: The smart meter is activated and can be used for automatic consumption data transmission
  • installed: The smart meter is installed
  • pre_installed: There is already a smart meter installed - no installation is needed
  • cancelled: The order has been cancelled
  • intended: The customer shows interest but has not yet completed the order
  • blocked: The order is artificially blocked by our system - waiting for admin approval
  • blocked_wim: The smart meter is blocked in Wechselprozess im Messwesen (WiM) - waiting for the network operator to confirm the installation
Available options:
waiting,
ordered,
checked,
installation_planning,
installation_scheduled,
installation_waiting,
installation_finished,
activated,
installed,
pre_installed,
cancelled,
intended,
blocked,
blocked_wim
Example:

"waiting"

created_at
required

Timestamp when the order was created

Example:

"2024-03-14T12:00:00Z"

updated_at
required

Timestamp when the order was last updated

Example:

"2024-03-14T12:00:00Z"