Mihonator/DocumentationIn development

For providers

From a header to your app

Add a setting in your panel. Follow its journey into the app. No HTTP experience needed.
On this page
Interactive walkthrough

A setting is just a name and a value.

In your panel, open Subscription → Settings → Response headers. Add one row for each setting.

SubscriptionSettingsExample panel

Try changing 74C7EC to A6E3A1. That is the same setting, with a mint green value.

Prefer a config file? Get the same settings as JSON.
Example panel configuration
{
  "customResponseHeaders": {
    "mihonator-hex": "74C7EC",
    "mihonator-servicename": "Your service",
    "mihonator-buyplan": "https://provider.example/plans",
    "mihonator-newboard": "true",
    "mihonator-custom": "update"
  }
}

These values go in the panel’s customResponseHeaders setting.

A place for each piece

Think of a subscription as a package. The URL is its address. Headers are the little notes attached to it.

In your panel
Add the notes under Subscription → Settings → Response headers. Each row has a key and a value. Save the changes.
On the subscription page
The import button passes the subscriber’s URL to the app. The service behind that URL delivers the configuration and headers.
Inside the YAML file
Put the connection settings: servers, proxy groups and routing rules. The appearance settings shown here belong in the HTTP response headers.

A change arrives with the next reply

Save a new color in your panel, then refresh the profile in the app. That fetches another copy of the subscription, including its headers.

In this example, mihonator-custom: update allows styling to be applied on refresh. The value add limits that to the first import.

This lesson illustrates the customization contract with sample data. See provider setup for metadata supported by current builds, or explore the full header reference.