Integration Guides &
API Documentation

Learn how to verify licensing states programmatically and whitelists daemon network protocols.

Chapters

Introduction Verification REST API Network & Firewalls Database Fallbacks

Introduction

The AMPNM licensing suite validates active host counts and performance footprints via cryptographic keys. Running background telemetry agents perform verification handshakes before streaming CPU, memory, and container allocations.

All licensing validation routes are hosted under our production domain **`https://portal.itsupport.com.bd`** which synchronizes directly with Cloud Firestore databases.

Verification REST API

To check license validity inside custom docker clusters or binaries, construct an HTTP request to the verify endpoints.

HTTP Request specifications:

Method: POST
Path: https://portal.itsupport.com.bd/api/license/verify
Content-Type: application/json

Request curl template:

curl -X POST https://portal.itsupport.com.bd/api/license/verify \
  -H "Content-Type: application/json" \
  -d '{"key": "AMPNM-DEVC-8F2B-9A4E-4321"}'

JSON Success Response (200 OK):

{
  "valid": true,
  "status": "active",
  "expiresAt": "2027-01-10",
  "orgId": "org-bb",
  "orgName": "Bangladesh Bank IT",
  "productId": "prod-cluster"
}

Network & Firewalls

For servers running behind enterprise routers or corporate firewalls, ensure outgoing packets whitelists whitelists the following target configurations:

Target Address	Port	Direction	Purpose
portal.itsupport.com.bd	443 (HTTPS)	Outgoing	License Verification Handshakes
telemetry.itsupport.com.bd	443 (HTTPS)	Outgoing	Metrics Stream Uploads

Offline Database Fallbacks