• Sandbox client — for first tests with this documentation
  • client_id

ezeep API Quick Guides

Goal of ezeep is to make the printing dramatically simpler. Before using the printing API, user should have to authorize and get the access token. Access tokens are the thing that applications use to make API requests on behalf of a user. The access token represents the authorization of a specific application to access specific parts of a user’s data.For ease of user in quick guide both authorization and printing are combined so that,user can easily perform all the steps.

Tip: the fastest way to get a working token for a quick experiment is the API Token Generator — it signs you in with your ezeep account and hands you a refresh token for the sandbox client below, ready to exchange for access tokens. This is for demo and ad hoc scripting only; for a real integration, register your own OAuth client (see Obtaining a ClientID for your Application).

Sandbox client — for first tests with this documentation

Only for ad hoc scripting and experimenting with the API. The client credential below is used in example requests throughout this documentation.

client_id

“yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB”

Resulting Authorization Header Authorization: Basic eWphdk53S3BkNEhnYlFlczBla1lIQkdqeElvc3pKZ2F5SWMwSmtkQjo= ### Allowed redirect_uris - “https://www.ezeep.com” - “http://localhost:3000/code” - “https://localhost:3333/” - “https://localhost:3333/auth-callback”