Pre-fill the ePaper Configurator from your own system

What this is for

The ePaper Configurator asks an installer a series of questions and produces a project spec plus the USB-preset config.xml that provisions the screens. If you are the CMS or the integrator, you already know most of the answers: the model, the fleet size, the content source, your player URL, how often the content changes.

Almost every answer can be supplied in the URL. Send that link and the customer lands on the first question still outstanding — usually just their Wi-Fi credentials — instead of a blank wizard.

The one exception is the “Anything special about the customer Wi-Fi?” step (hidden SSID, band steering, captive portal, WPA3, proxy, and so on). Those are tick-boxes and have no URL parameter, so the customer answers them in the wizard. That is usually the right way round: they describe the site, and you would be guessing.

The quickest way — let the tool write the link

You do not have to hand-write URLs.

1. Open the Configurator and fill it in as if you were doing the deployment.
2. On the finished spec, press 🔗 Copy pre-filled link.
3. Paste that link into your onboarding e-mail, your documentation, or a button in your own portal.

The generated link carries every answer except Wi-Fi / 802.1X credentials and the project contact fields — those are deliberately left out, because a link travels through mail scanners, chat logs and browser history.

Building the link yourself

Base URL:

https://epaper-setup.samsungedo.com/

Append the answers you know as ordinary query parameters:

https://epaper-setup.samsungedo.com/?model=em13dx&qty=200&deploy=usb
    &conn=wifi&sec=psk&dhcp=true
    &tep=yes&tepapp=YourCMS&url=https://player.yourcms.example/device
    &power=battery&changes=daily&recharge=monthly
    &orient=Landscape&tnc=agree

How it behaves

• Answers you supply are applied, then the wizard jumps to the first question still missing — so an incomplete link tells the customer exactly what is outstanding.
• A "Pre-filled from link" banner appears, so the customer knows the answers came from you.
• Unknown or invalid values are ignored, never trusted. A misspelled model= simply leaves that question unanswered rather than producing a wrong configuration.
• Add spec=1 to land straight on the finished spec (only if nothing is missing).

Parameters

Device & deployment

Network

Content — this is the part that is yours

Power & battery

Housekeeping

Partner edition — your name on it

Add partner= (and optionally your player URL) and the link becomes a partner edition: the content source is locked to your app, the content question is skipped when it is fully determined, and a banner keeps your attribution visible throughout.

https://epaper-setup.samsungedo.com/?partner=YourCMS&url=https://player.yourcms.example/device

This is the shape to publish in your own onboarding documentation, so your customers never have to work out which content source to pick.

Worked example

200 × 13″ screens, wall-mounted landscape, on battery, content changing once a day, joining a WPA2 network by USB preset, showing your CMS:

https://epaper-setup.samsungedo.com/?model=em13dx&qty=200&deploy=usb
  &conn=wifi&sec=psk&ssid=SITE-IOT&dhcp=true
  &tep=yes&tepapp=YourCMS&url=https://player.yourcms.example/device
  &power=battery&changes=daily&recharge=monthly
  &orient=Landscape&tnc=agree&project=Store%20Rollout

The customer opens this and is asked only for their Wi-Fi password. Everything else — the deployment steps, the firewall rules their IT needs to open, the battery expectation and the config.xml — is already there.

Five things worth knowing before you ship it

2. Omitted answers take sensible defaults silently. If a project depends on a particular value, pass it explicitly rather than relying on the default: conn=wifi, dhcp=true, pin=000000, tnc=agree, orient=Portrait.

3. tnc=agree is mandatory for any cloud content source. The screen must reach the internet during first-time setup to accept the terms, or content never starts.

4. Deep Sleep + a CMS means your app owns the wake. In Deep Sleep both radios are off and there is no built-in refresh timer for a custom app — the panel only updates if your application schedules its own wake. No configuration file can add a wake driver. If your player does not schedule wakes yet, do not send sleep=DeepSleep.

5. Certificates are never passed by URL — only their file names. The files themselves are placed on the USB stick manually.

Get your CMS pre-filled

If your player endpoint is a fixed, published address, we can pre-fill it automatically whenever a customer selects your CMS — they then have nothing to type at all. Send us the exact device/player URL and we will add it. We deliberately never guess an endpoint, because a wrong one fails silently.

The same applies to being listed in the CMS picker: if your integration is live and you are not in the partner directory, tell us and we will add you.

Open the Configurator CMS partner directory