Plan an application that prints with ezeep
Use the ezeep REST API to add printer discovery, document submission and job tracking to your application.
On this page
- Connect a printer, give the application’s account access and test printing
- Choose a shared printing account or separate sign-in for each user
- Choose direct API development or an MCP-assisted build
- Match each API operation to its documented host and endpoint
- Authenticate, submit a test print and check its status and output
[Step] 1. Connect a printer, give the application’s account access and test printing
Create an organization, connect a printer and assign it to the identity your application will use. Confirm a normal print works before testing the API.
[/Step]
[Step] 2. Choose a shared printing account or separate sign-in for each user
One shared ezeep identity
Use this for a kiosk, internal tool or server-side workflow that prints as one account. For an integration built with MCP assistance, use the documented pairing flow: request a pairing code, sign in at its returned URL, then exchange the code for tokens.
Each user signs in separately
Use per-user OAuth for a product where users print through their own ezeep accounts. Public clients use Authorization Code with PKCE. Register or reuse the application’s OAuth client, then implement its sign-in flow.
Do not replace per-user sign-in with instructions for users to copy and paste refresh tokens. The token generator is for developer evaluation.
[/Step]
[Step] 3. Choose direct API development or an MCP-assisted build
An AI client connected to ezeep MCP can read the integration guide, API reference and code examples, then help build the integration. A conventional deployed application calls the REST API directly; agent applications can use MCP as their ongoing interface.
For an MCP-assisted build, ask:
“Read the ezeep integration guide and API reference. Help me add printing to this application using [shared-account or per-user] authentication. Start by checking the account, printer and authentication requirements.”
[/Step]
[Step] 4. Match each API operation to its documented host and endpoint
|
Host and path |
Use |
|---|---|
|
printapi.ezeep.com/sfapi/ |
User-visible printers, capabilities, file upload preparation, print submission, status and supported file types. |
|
api2.ezeep.com/printing/v1/ |
Printer, group and connector management. Follow pagination. |
|
account.ezeep.com/v1/ account.ezeep.com/oauth/ account.ezeep.com/auth/ |
Account, user and OAuth operations. Use the exact endpoint for the operation. |
Use the exact paths and trailing slashes from the reference. There is no single base URL for all operations.
[/Step]
[Step] 5. Authenticate, submit a test print and check its status and output
Authenticate the application, then submit and track a test print. After that, add your workflow’s error handling and token renewal.
Keep application secrets and tokens in the backend. Store rotating refresh tokens in writable, protected storage and replace the stored value after every refresh.
Check current plans and API quotas before rollout. User-triggered printing has no per-page limit for licensed users. Automated printing has a separate plan allowance; check the current allowance and any overage charges.
The API documentation is the reference for endpoint schemas. If your organization cannot register the client it needs, use the API contact form.
[/Step]