Reolink · JSON Structure

Reolink Device Structure

Structural documentation for Reolink camera and NVR device resources

Type: object Properties: 0
IoTSecurity CamerasSurveillanceSmart HomeAI Detection

Reolink Device Structure is a JSON Structure definition published by Reolink.

Meta-schema:

JSON Structure

Raw ↑
{
  "title": "Reolink Device Structure",
  "description": "Structural documentation for Reolink camera and NVR device resources",
  "type": "object",
  "structure": {
    "DevInfo": {
      "type": "object",
      "description": "Camera or NVR device information",
      "properties": {
        "model": {
          "type": "string",
          "description": "Device model name",
          "example": "RLC-810A"
        },
        "serial": {
          "type": "string",
          "description": "Device serial number",
          "example": "00000000000000"
        },
        "firmVer": {
          "type": "string",
          "description": "Firmware version string",
          "example": "v3.1.0.2368_23062507"
        },
        "hardVer": {
          "type": "string",
          "description": "Hardware version",
          "example": "IPC_523128M8MP"
        },
        "channelNum": {
          "type": "integer",
          "description": "Number of camera channels",
          "example": 1
        },
        "name": {
          "type": "string",
          "description": "Device configured name",
          "example": "Backyard Camera"
        },
        "wifi": {
          "type": "integer",
          "description": "WiFi capability flag (0=no, 1=yes)",
          "example": 1
        }
      }
    },
    "Token": {
      "type": "object",
      "description": "Authentication token from login",
      "properties": {
        "name": {
          "type": "string",
          "description": "Token string used in query parameter",
          "example": "sample123token456"
        },
        "leaseTime": {
          "type": "integer",
          "description": "Token validity duration in seconds",
          "example": 3600
        }
      }
    },
    "PtzCtrl": {
      "type": "object",
      "description": "PTZ control command parameters",
      "properties": {
        "channel": {
          "type": "integer",
          "description": "Camera channel number (0-based)",
          "example": 0
        },
        "op": {
          "type": "string",
          "description": "PTZ operation: Stop, Left, Right, Up, Down, ZoomInc, ZoomDec, ToPos",
          "example": "Left"
        },
        "speed": {
          "type": "integer",
          "description": "Movement speed 1-64",
          "example": 32
        },
        "id": {
          "type": "integer",
          "description": "Preset ID for ToPos operation",
          "example": 1
        }
      }
    },
    "SearchResult": {
      "type": "object",
      "description": "Recording search result with day/time bitmap",
      "properties": {
        "channel": {
          "type": "integer",
          "description": "Camera channel"
        },
        "Status": {
          "type": "array",
          "description": "Array of months with recording status bitmaps"
        }
      }
    }
  }
}

Work with this as data

Every JSON Structure here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Structure
curl "https://apis.io/api/v1/json-structures/reolink-device-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.