NebularStack
Website

Subscriber FUP API

Overview

This API provides programmatic access to manage Fair Usage Policies (FUPs) and their rules. It is the same data used by the console UI. For a complete explanation of how FUPs behave — thresholds, cycles, how multiple rules stack, and why the subscriber's timezone matters — see Fair Usage Policies.

A FUP profile is a named container that holds one or more rules. Each rule reduces speed once a data threshold is reached within a daily, weekly, or monthly cycle. A FUP profile is applied to a subscriber profile, and every subscriber on that profile inherits the policy.

The typical workflow is:

  1. Create a FUP profile — POST /v1/fup.

  2. Add one or more rules to it — POST /v1/fup/{fup_id}/rule.

  3. Apply the FUP profile to a subscriber profile using the Subscriber Profiles API.

FUP Profiles

Manage the FUP profile — the named container that rules belong to.

GET
/v1/fups
(subscriber)

List FUPs
Service
subscriber
GET
/v1/fup/{fup_id}
(subscriber)

Get a single FUP
Service
subscriber
POST
/v1/fup
(subscriber)

Create a FUP
Service
subscriber
PATCH
/v1/fup/{fup_id}
(subscriber)

Update a FUP
Service
subscriber
DELETE
/v1/fup/{fup_id}
(subscriber)

Delete a FUP
Service
subscriber

FUP Rules

Each rule belongs to a FUP profile and defines a single throttling condition. See Fair Usage Policies for the meaning of each field:

  • chain — the traffic the rule measures: download, upload, or combined.

  • cycle — the counter the rule watches and when it resets: daily, weekly, or monthly.

  • volume_threshold — data used (in GB) before the rule takes effect.

  • download_reduction_percent / upload_reduction_percent — how much to cut each direction of speed (0–100).

  • start_hour / end_hour — the time-of-day window the rule is active. These hours are in UTC.

  • rule_order — the order the rule is evaluated in.

GET
/v1/fup/{fup_id}/rules
(subscriber)

List FUP Rules
Service
subscriber
GET
/v1/fup/{fup_id}/rule/{rule_id}
(subscriber)

View a Single FUP Rule
Service
subscriber
POST
/v1/fup/{fup_id}/rule
(subscriber)

Create a FUP Rule
Service
subscriber
PATCH
/v1/fup/{fup_id}/rule/{rule_id}
(subscriber)

Update a FUP Rule
Service
subscriber
DELETE
/v1/fup/{fup_id}/rule/{rule_id}
(subscriber)

Delete a FUP Rule
Service
subscriber