Skip to main content
POST
/
device
/
heartbeat
Heartbeat
curl --request POST \
  --url https://api.telluspower.example.com/v1/device/heartbeat \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "timestamp": "2025-03-15T10:30:00Z",
  "status": "online",
  "fault_code": 0
}
'
{
  "code": 123,
  "message": "<string>",
  "data": {
    "commands": [
      {
        "command_id": "<string>",
        "command": "<string>",
        "params": {},
        "expiry": "2023-11-07T05:31:56Z"
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://developers.telluspowergroup.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

Authorization
string
header
required

Charger-side bearer token. Obtained by exchanging device_id and device_secret (issued at registration) at /v1/device/token. Valid for 24 hours.

Body

application/json
timestamp
string<date-time>
required
status
enum<string>
required
Available options:
online,
offline,
fault
fault_code
integer
required

0 = no fault; otherwise platform-defined code.

Response

200 - application/json

Heartbeat acknowledged. Pending commands may be returned.

Standard response envelope. code is 0 on success and a non-zero application code on error (see Error Codes — §14).

code
integer
required

0 = success; otherwise an error code per the Error Codes section.

message
string
required

Human-readable description.

data
object

Endpoint-specific payload.