Oktopus Controller Docs
Contact
  • Welcome
  • Getting Started
    • About
    • Architecture
    • Requirements
      • Network
    • Installation
      • Standalone
      • High Availability
      • FAQ
    • Community Edition
    • Enterprise Edition
      • Scripts
    • Integrations
  • Device Configuration
    • Simulators
      • (USP) Agent Simulator
    • Open Source Platforms
      • PrplOS
      • OpenWRT
  • USP (TR-369)
    • Introduction
    • Architecture
    • MTPs
      • MQTT
  • CWMP (TR-069)
    • Introduction
    • Architecture
  • Reference
    • Bibliography
Powered by GitBook
On this page
  • REST API
  • NATS

Was this helpful?

Edit on GitHub
  1. Getting Started

Integrations

PreviousScriptsNextSimulators

Last updated 8 months ago

Was this helpful?

Alright, you've just setup Oktopus to manage all your multi-vendor devices, hoping it to be a one platform, with one UI to solve all your problems, but then suddenly you realize that you have other systems and software for different purposes but you wish all those solutions to converge into a coesive ecosystem.

For this matter Oktopus provides two alternatives:

REST API

To integrate Oktopus into your ecosystem, you can rely on . It's documented in Postman, with many usage examples in different programming languages, and lots of possibilities.

NATS

For advanced users who may need real time information and have experience with PUB/SUB messagery concepts, it's also possible to use NATS.

Oktopus Controller REST API