Make every megabyte print more

The standard 50 MB monthly allowance can support over 20,000 compact text-only labels—or up to 25,600 jobs when the gateway downloads each document directly from your secure URL.

What 50 MB means in practice

A 50 MB allowance contains 52,428,800 bytes. A compact text-only file averaging about 2.5 KB or less can therefore provide more than 20,000 uploaded labels. Fonts, logos, images, barcodes and PDF-generator overhead can change the result substantially.

Headline capacity: each secure direct-URL job uses 2 KB, giving the standard 50 MB plan capacity for up to 25,600 print jobs per monthly period.

How usage is calculated

• Gateway-direct URL: exactly 2,048 bytes per job, regardless of the downloaded document’s size.
• Uploaded or inline document: at least 2,048 bytes, then rounded upward to the next 512-byte increment.
• Copies: do not multiply usage because AppClickPrint transfers the source document once.
• Portal test print: free and excluded from usage.
• Diagnostics: the gateway’s actual downloaded byte count is retained separately and does not change the direct-URL job’s 2 KB debit.

Create smaller uploaded print files

• Prefer text and vector lines over screenshots or full-page raster images.
• Use PDF standard fonts where practical, or subset embedded fonts to include only the characters used.
• Crop images tightly and resize them to the printer’s actual output resolution.
• Use grayscale or monochrome assets for monochrome label and receipt printers.
• Create a print-specific logo instead of embedding a full-resolution website image.
• Generate the PDF page at the exact physical widthMm and heightMm.
• For compatible printers, consider compact native ZPL or ESC/POS commands.
• Measure and record the final generated file size in your backend before submission.

Get the most value with documentUrl

When a document already exists in your application’s object storage, submit its secure URL instead of uploading the file. AppClickPrint passes the URL to the selected Android, Windows or Linux gateway, which downloads it directly from your storage.

curl -X POST "https://appclickprint.com/v1/printers/reception-label/print" \
  -H "Authorization: Bearer acp_CUSTOMER_PRINT_KEY" \
  -F "format=pdf" \
  -F "documentUrl=https://files.example.com/signed/label-94827.pdf" \
  -F "filename=label-94827.pdf" \
  -F "widthMm=62" \
  -F "heightMm=29" \
  -F "copies=1" \
  -F "photoMode=false" \
  -F "idempotencyKey=visitor:94827:badge:v1"

URL requirements

• Use an HTTPS URL the customer’s gateway can access without private application cookies or custom request headers.
• Prefer a high-entropy, short-lived signed URL rather than a permanently public document.
• Keep it valid long enough for a temporarily offline gateway to reconnect and download the job.
• Do not replace the file at the signed URL after submitting the job.
• The PDF page must still match the submitted physical dimensions.
• Optional Boolean photoMode overrides the saved printer setting for this PDF: true improves photographs, false favours text and barcodes, and omission inherits the saved setting.
• Provide exactly one source: document, documentUrl, inline data or dataBase64.

Before releasing

1. Generate representative labels with and without images and measure their final sizes.
2. Use documentUrl for documents already stored securely by your application.
3. Test signed URLs while the gateway is online and after a short offline delay.
4. Use a stable idempotency key when retrying print submission.
5. Handle HTTP 429 with backoff and handle monthly_print_limit_reached clearly.

Print API guide Pricing Billing fine print