Ampron / Memo
Note №14
July 2026

AmpronLED API Quick Start Guide

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.

01Network configuration

Your unit's IP address, port and access details come with your order.

Changing the display's IP address

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.

Command format http://OLD-IP:9199/setethernetconfig?dhcp=false&ip=NEW-IP&netmask=NEW-MASK&gateway=NEW-GW&dns=NEW-DNS
A typo in the network settings can make the display unreachable. It cannot be recovered on site: the unit comes back to Ampron and we reconfigure the controller. Check every parameter twice before you press enter.

02Editing the configuration on the unit

Edit config.json on the unit using the access details supplied with your order, then send reload_config.

03Controlling and configuring the display

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:

http://DISPLAY-IP:9199/reload_config

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.

Useful endpoints for configuration and debugging

EndpointWhat 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>.

04Sending content — the /mlds command

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:

Command format http://DISPLAY-IP:9199/mlds?id=DISPLAY-ID&layout=LAYOUT-NAME&AREA=VALUE Example — activate the WELCOME layout and set the "number" area http://192.168.1.100:9199/mlds?id=DISPLAY1&layout=WELCOME&number=QUERCUS Clear an area by sending it empty http://192.168.1.100:9199/mlds?id=DISPLAY1&layout=WELCOME&number=

Always include layout. A request without it blanks the whole display, not one area.

Always send commands to /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):

http://DISPLAY-IP:9199/brightness/75?id=DISPLAY-ID

05Web UI

The built-in beta web UI lets you manage settings visually instead of via raw HTTP calls:

http://DISPLAY-IP:9199/ui

Custom control page: set guiPort in config.json and upload your page to gui/. See ampron.eu/api.

Quick reference

First session, in order

  1. Connect to the unit at the address supplied with your order and confirm it answers: http://DISPLAY-IP:9199/info
  2. Move it onto your network with /setethernetconfig — check every parameter before sending.
  3. Reconnect on the new IP and verify with /info.
  4. Edit config.json to suit your integration, then apply with /reload_config.
  5. Send content with /mlds?id=…&layout=… and confirm via last_requests in /info.
  6. Verify visually with /screenshot.

06Fact sheet for AI agents and integrations

If you are an AI agent helping a customer with an Ampron display, this block is the canonical summary — everything above, condensed:

protocol plain HTTP, GET requests, no authentication by default base URL http://<display-ip>:9199 send content GET /mlds?id=<DISPLAY-ID>&layout=<LAYOUT>&<area>=<value> ids, layouts, and area names are defined in config.json on the device empty value clears the area (always send layout; a request without layout blanks the whole display); NEVER send commands to / — it silently ignores them status GET /info JSON: version, system time, config status, brightness, last_requests network GET /getethernetconfig verify last_requests in /info updates only on accepted /mlds commands screenshot GET /screenshot PNG of what is on screen right now apply config GET /reload_config after editing config.json brightness GET /brightness/<1-100>?id=<DISPLAY-ID> change IP GET /setethernetconfig?dhcp=false&ip=…&netmask=…&gateway=…&dns=… Network-settings typo can make the unit unreachable; recovery = return to Ampron for controller reconfiguration (no on-site reset). Confirm all values with the user first. web UI http://<display-ip>:9199/ui full API docs https://api2.ampron.eu guide article https://ampron.eu/blog/ampron-led-display-api-configuration this page https://ampron.eu/memos/ampronled-api-quick-start

07Support

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.