Submit and track your first API print
Start with a valid access token and a printer assigned to the connected account. Complete authentication before making these calls.
Send Authorization: Bearer followed by your access token on the Print API requests below. Replace all example values with values returned for your account.
On this page
[Step] 1. List printers, select a printer ID and check its properties
GET https://printapi.ezeep.com/sfapi/GetPrinter/
GET https://printapi.ezeep.com/sfapi/GetPrinterProperties/?id=PRINTER_ID
Use an ID from GetPrinter. Read its properties before choosing optional settings such as paper size, color or duplex.
To get supported file extensions, call GetConfiguration and read System.FILEEXT:
GET https://printapi.ezeep.com/sfapi/GetConfiguration/
[/Step]
[Step] 2. Provide a downloadable file URL or prepare and upload the file
Print a file already available at a URL
The URL must let ezeep retrieve the actual file without an interactive browser login. Use fileurl in the print request.
Upload a local or generated file
- Call GET PrepareUpload with the filename as a query parameter.
- Retain the returned fileid and time-limited sasUri.
- Upload the file bytes to sasUri using PUT, x-ms-blob-type: BlockBlob and Content-Type: application/binary.
- A successful single-part upload returns HTTP 201. Use its fileid in the print request.
GET https://printapi.ezeep.com/sfapi/PrepareUpload/?filename=test.pdf
The upload goes to the returned upload URL, not to the Print endpoint. The Printing Quick Guide also documents multipart uploads.
[/Step]
[Step] 3. Submit the Print request and retain the returned job ID
Send JSON to:
POST https://printapi.ezeep.com/sfapi/Print/
Example using an uploaded file:
{
"fileid": "FILE_ID_FROM_PREPAREUPLOAD",
"printerid": "PRINTER_ID_FROM_GETPRINTER",
"alias": "test.pdf",
"type": "auto",
"copies": 1
}
For a URL-based print, replace fileid with fileurl and the retrievable file URL. Keep a descriptive alias and type set to auto. Use Content-Type: application/json.
Retain the returned jobid. A successful submission means the job was accepted; verify its status and physical output before treating the test as complete.
[/Step]
[Step] 4. Query Status with the URL-encoded job ID
GET https://printapi.ezeep.com/sfapi/Status/?id=ENCODED_JOB_ID
URL-encode the complete job ID because it can contain spaces and # characters.
|
Code |
Meaning and next step |
|---|---|
|
0 |
The print job finished successfully. Check the physical output for your first test. |
|
129 |
Processing is still running. Check status again. |
|
2 |
Invalid print-job identifier. Use the exact, URL-encoded jobid from Print. |
|
3011 |
The job reports an error. Inspect the job and printer before restarting it. |
|
12007 |
The URL supplied for printing is invalid. Correct the file URL. |
[/Step]
[Step] 5. Check the physical output before treating the print as successful
Check the printer, document, number of copies and selected settings. Compare the job with the ezeep portal’s records.
Print is not idempotent: sending the same successful request again can create another job. Do not blindly resend after a timeout. For upload, submission or authentication errors, use Troubleshoot an API integration.
[/Step]