Skip to main content
Every organization has a test mode with its own keys (pe_test_), its own webhook endpoints and a virtual computer called PrintEasy Test Computer. Test jobs walk from queued to done in about 3 seconds through the same code as live jobs, so webhooks, the event feed and the dashboard behave exactly as they will in production. The mode comes from the key. A pe_test_ key only sees test data and a pe_live_ key only sees live data, so a resource of the other mode answers 404. In the dashboard, the Test mode toggle filters every list the same way.

​
Test printers

PrintEasy Test Computer has four printers. They are created the first time you use test mode. Only pe_test_ keys can target these printers, and test keys can only target them. Sending a job to the wrong mode answers 422 mode_mismatch. See Raw printing for the two raw printers.

​
Forcing an error

Put [fail] anywhere in the job title and the job ends in error instead of done, so you can test your error handling and your printjob.error webhook handler:

​
Limits

Test mode is free and nothing is printed on paper. Each organization can create 500 test jobs per day (a UTC day). Past that, POST /v1/printjobs answers 429 test_mode_daily_cap until the next day. Test jobs never count toward your plan’s prints; GET /v1/usage reports your live usage for the current period.

​
Switching to live

When your integration works against the test printers:
  1. Install the agent on a computer with a real printer and mark the printer live.
  2. Create a live key (it starts with pe_live_) and use it instead of the test key.
  3. Create live webhook endpoints. Test endpoints never receive live events. Live endpoints must use https:.
  4. Replace the test printer ids with the ids from GET /v1/printers on the live key.
Nothing else changes: the same requests, the same states and the same webhook payloads.