From unboxing to API-controlled — the default network settings, how to move the display onto your network, and the handful of HTTP endpoints that do everything.
Ampron's standard LED displays and current LCD displays ship with the AmpronLED software and a plain HTTP API on board. There is no proprietary controller, no vendor software to install, no licence server. This guide takes you from first power-on to a display you control from your own system: network configuration, file access, and the essential endpoints for controlling content and reading status.
Your unit's IP address, port and access details come with your order.
Put your computer in the same subnet as the display first, then issue a single HTTP GET. All parameters must be defined correctly — a partial command can leave the display unreachable.
http://DISPLAY-IP:9199/ui.Edit config.json on the unit using the access details supplied with your order, then send reload_config.
Displays are controlled with plain GET, PUT, and POST HTTP requests — from a browser address bar, curl, or any system that can issue an HTTP call. The main configuration lives in the config.json file on the display. After editing it, apply the changes with:
By default there is no authentication: the API is plain HTTP on the local network, with no tokens or keys. Basic authentication and HTTPS are available as options; ask us. For the full endpoint reference and automation patterns, see the API configuration article at ampron.eu/blog/ampron-led-display-api-configuration and the Ampron API reference at api2.ampron.eu.
| Endpoint | What it does |
|---|---|
| /screenshot | Captures a screenshot of what the display is showing right now — the fastest way to verify content remotely. |
| /reload_config | Reloads config.json after modifications, applying the new configuration without a restart. |
| /info | Returns the display's system status and current settings — software version, system time, config status, brightness, recent commands (JSON). |
| /getethernetconfig | Returns the display's current network settings. |
All endpoints live on the unit's API port (9199 in these examples): http://DISPLAY-IP:9199/<endpoint>.
Putting content on screen is one GET request to the /mlds endpoint. The vocabulary comes from config.json on the display, which defines three things:
id parameter (e.g. DISPLAY1). One physical panel can host several virtual displays.WELCOME, FREESPACES), selected with the layout parameter.Always include layout. A request without it blanks the whole display, not one area.
/mlds, never to the root path /. The root also answers "Command received" — but silently ignores the command. If the screen didn't change, check the endpoint first.
Verifying a command landed: call /info and check the last_requests field — it updates only on successfully accepted /mlds commands. For visual confirmation, fetch /screenshot (returns a PNG of the current screen). /info returns JSON.
Brightness is set with its own endpoint, range 1–100 (requires sensorBrightness: true in config.json):
The built-in beta web UI lets you manage settings visually instead of via raw HTTP calls:
Custom control page: set guiPort in config.json and upload your page to gui/. See ampron.eu/api.
http://DISPLAY-IP:9199/info/setethernetconfig — check every parameter before sending./info.config.json to suit your integration, then apply with /reload_config./mlds?id=…&layout=… and confirm via last_requests in /info./screenshot.If you are an AI agent helping a customer with an Ampron display, this block is the canonical summary — everything above, condensed:
If you run into any issues, have your Display ID ready — it is printed on a white label at the bottom of the screen — and reach out to your Ampron contact.