In short: Server Direct Print (SDP) is Epson’s name for the function that lets a receipt printer fetch its own work. The printer asks a web address you set on it, again and again, and the answer is either empty or the receipt to print. Nothing in the venue’s network has to accept a connection from outside, and in return a job never arrives sooner than the printer’s next request.
NoteWhat this article rests on
The message formats follow revision K of Epson’s Server Direct Print manual (2016). They were read against an open-source implementation and one poll captured from a current Epson printer in October 2026. Epson’s reference guide for a current printer family was used for the feature, the setup tools and the first administrator password, not for the formats. Epson’s overview of a newer revision, U (August 2023), was readable only as a list of printers, so where Epson ties a point to some printers or firmware, the text says so.
One exchange, step by step
Every exchange is started by the printer: it posts a poll and gets the answer, and when the answer held a job it then posts the result and gets an empty 200.
The poll. At the interval set on the printer, it sends an HTTP POST to the address in its settings. The body is a form with ConnectionType=GetRequest and ID, the value set on the printer, which is empty when none was set. On the screens Epson’s manual shows for some printers, the interval runs from the end of one exchange to the start of the next. The captured poll also had a Name field, the printer’s own device name, which the 2016 manual does not list: a server should ignore fields it does not know.
POST /sdp HTTP/1.1
Content-Type: application/x-www-form-urlencoded
ConnectionType=GetRequest&ID=
The answer. With nothing to print, the server returns an empty 200 with Content-Type: text/xml. With a job, it returns XML. This one prints a line and cuts the paper:
<?xml version="1.0" encoding="utf-8"?>
<PrintRequestInfo Version="2.00">
<ePOSPrint>
<Parameter>
<devid>local_printer</devid>
<timeout>10000</timeout>
<printjobid>ABC123</printjobid>
</Parameter>
<PrintData>
<epos-print xmlns="http://www.epson-pos.com/schemas/2011/03/epos-print">
<text>Hello </text>
<cut type="feed"/>
</epos-print>
</PrintData>
</ePOSPrint>
</PrintRequestInfo>
The result. The printer posts again, with ConnectionType=SetResponse and a ResponseFile field holding XML. Without a spooler it does so after printing. With the spooler on, which Epson lists for some printers and firmware, it posts as soon as it has accepted the job, which can be before the paper moves (see “What it does not give you”). Its response element has success, a code and a status. The server answers with an empty 200. The sample below is shortened.
POST /sdp HTTP/1.1
Content-Type: application/x-www-form-urlencoded
ConnectionType=SetResponse&ID=&ResponseFile=<PrintResponseInfo Version="2.00">…</PrintResponseInfo>
What the answer can carry
- A version. In the 2016 manual,
PrintRequestInfois 1.00 (also used when none is given), 2.00, which addsprintjobidso the result can name its job, or 3.00, which it lists for only a few printers. Its table ties 2.00 to some printers and firmware as well. Epson warns that the versions are not compatible and says to check the printer before use, and the result’s format follows the version. - Jobs and a timeout. One answer may hold several
ePOSPrintelements.timeoutis in milliseconds: if it passes after printing has started, the printer cancels the job, but what it has already read is printed. - The page. Print data is ePOS-Print XML: Epson’s elements such as
text,feedandcut, or acommandelement with raw ESC/POS commands as hexadecimal text. The printer’s ePOS-Print setting must not be off, and for some printers Epson’s manual shows an error report for that case. - Limits. UTF-8 only, no byte order mark, and a maximum size that depends on model and firmware. For early firmware of Epson’s intelligent printers at the faster print speed the manual gives 200.0 KB.
This minimal server hands out one job, then answers every poll with an empty 200. A real one keeps the job until its result arrives or a time limit passes, and checks who is asking: Epson’s manual describes Digest authentication, and Tillcast uses a secret in the address.
To play the printer, run curl -i -X POST http://127.0.0.1:8080/sdp -d 'ConnectionType=GetRequest&ID=': the first call returns the job, the next ones an empty answer.
What the printer needs
- A printer that has the feature. Epson’s overview of the manual (revision U) lists the printers that support it: its intelligent printers, with minimum software versions for older ones, and a number of other printer lines. Epson’s product pages and specification sheets for some current models name the feature (one of each is under Sources). A family name does not settle it, so check the variant.
- Settings on the printer. Epson’s manuals put them in its setup utility and in Web Config, the printer’s built-in web page, which you open by typing the printer’s IP address into a browser. On the family in Epson’s reference guide, the first administrator password is on a label or is the serial number. The manual’s fields include: on or off; one or more addresses (up to three on newer firmware), each with an interval; an ID and password; and a switch to check the server’s certificate over HTTPS.
- Firmware. On older software of Epson’s intelligent printers the manual gives a single address, and HTTPS only from a minimum version; it lists the minimum software each series needs. The smallest interval a current printer accepts is not in the sources read.
- A network path. The printer must reach the server: outbound HTTP or HTTPS, and DNS if the address is a host name. Epson positions the feature for cloud printing and online ordering, and its specification sheet says cloud printing requires an internet connection; the protocol itself needs only a network path to the server.
Running it yourself or using Tillcast
A printer with Server Direct Print needs a web server to talk to. You can install and run one yourself, on a computer at the venue or on a server in the cloud, or use Tillcast, which is that server as a service.
| A server you install and run | Tillcast, in the cloud | |
|---|---|---|
| What you write | The poll and result handlers shown above, a job queue, a way to tell who is asking (Digest authentication, or a secret in the address) and HTTPS if you want it | One API call that creates a job from a document of blocks |
| Who builds the commands | Your code writes the ePOS-Print XML | Tillcast turns the document into the printer’s commands when it accepts the job |
| Where the printer points | At your server, which must be reachable from the printer and needs a certificate for HTTPS | At the printer URL that Tillcast gives you |
| Many venues and printers | Yours to build: addresses, customers, status | Customers, locations and printers are part of the API |
| The result | You read the second request and keep the status | The job shows queued, delivered and printed, or failed, expired or cancelled |
| Who keeps it running | You, and the computer at the venue if there is one | Tillcast |
Another Epson route, ePOS-Print, sends the job to the printer’s own address at /cgi-bin/epos/service.cgi, so the sender must be able to reach the printer. Server Direct Print needs no open port at the venue.
What it does not give you
- Instant delivery. The manual describes only periodic requests, so a job created just after a poll waits for the next one.
- Detail after “accepted”. With the printer’s spooler on, which Epson lists for some printers and firmware,
successcomes back when the printer has taken the job in, which can be before the paper moves. A cover opened or paper out after that is not reported in the job’s result. - A way to ask. A server cannot query the printer. Without Status Notification it learns the printer’s state only from the status in each result and from the polls stopping. Status Notification is a separate Epson function with its own address.
Security notes
- Outbound only. The printer opens the connection, so the venue needs no inbound port or VPN.
- HTTPS, optionally with the server checked. Epson’s manual describes HTTPS with optional server authentication against certificates registered on the printer, and says SSL 3.0 is not supported. TLS versions depend on model and firmware. Certificates have validity dates, so a wrong clock can make a valid one fail on a printer that checks them: set the date and time first. Epson’s manual does not say whether the printer checks the dates.
- Digest authentication. Epson lists it for some printers and firmware. With an ID and a non-empty password, the printer sends a dummy request, gets a
401, and repeats it with credentials. The ID also travels as a plain form field in every poll, so it names the printer and is not a secret. - A secret address is a credential. If the address is the only credential, as with a secret in the URL, anyone who learns it can poll it and read the jobs, or post results as the printer. Check every request, and change the printer’s default administrator password, as Epson recommends.
How Tillcast uses it
Tillcast supports Epson printers with Server Direct Print, and documents print on them. The full test page has been printed on one Epson printer with Server Direct Print. You can add an Epson printer with Server Direct Print through the API. Documents print on it, and so does Test print.
A document you send to an Epson printer is turned into the printer’s commands when Tillcast accepts the job, and the printer prints it the next time it asks for work. With the printer’s spooler on, an Epson reports a job as printed when it has accepted the page, so a cover opened or paper out after that is not reported. An Epson printer has a few more settings to check than a Star one, such as ePOS-Print and the check of the server’s certificate, and it may need a certificate imported.
- The printer asks its Tillcast address for work, as it does at every interval, and gets an empty answer.
- Your software creates a job with one HTTPS call to the API.
- Tillcast turns the document into the printer's commands and queues the job.
- At its next poll the printer gets the job in the answer, as XML with the commands in hexadecimal. The job is delivered.
- The printer takes the job in and prints it.
- The printer posts its result. With the spooler on, it posts once it has accepted the page, which can be before the paper moves. The job is printed when the printer reports success.
- Your software reads the job and sees its status.
- The address is the credential. It is shown once, when the printer is added, and the ID and password on the printer are left empty (the printer URL). Set up an Epson printer has the steps and suggests an interval of 5 seconds.
- A job that was handed over is not sent again. With no result within about two minutes it ends
failedwith the reasonresult_missing, although it may have printed, so look at the paper before you print again (jobs). - A printer that has connected and has not polled for about 4 minutes has the status offline.
- Supported printers says what has run on a device, and the security page lists what is built.
Sources
All read in October 2026.
- Epson, Server Direct Print User’s Manual, Rev.K (M00062910): messages, versions, settings, limits.
- Epson, overview of the Rev.U manual (21 August 2023): the list of printers.
- Epson, Technical Reference Guide for a current printer family, Rev.F: the feature, the setup tools, the first administrator password.
- Epson, ePOS-Print XML User’s Manual, Rev.K: the
commandelement and the printer’s web service. - Epson America, specification sheet (CPD-62919): the feature for cloud printing and online ordering, and the internet-connection note. Epson Europe’s product page: that Epson names the feature.
- ReceiptLine, a Server Direct Print example (Apache-2.0): an open-source implementation, not Epson’s.