• Public ClientID, Redirect URI for First Tests with this Documentation
  • client_id

ezeep API Quick Guides

Before using the Print API, a user has to authorize your application and you need an access token. Applications use access tokens to make API requests on behalf of a user. An access token represents the authorization of a specific application to access specific parts of a user’s data. The Printing Quick Guide combines authorization and printing in one sequence of steps.

Other quick guides:

• Organization & User Management Quick Guide
• Download Monthly Reports Quick Guide

To get a token for testing, use the API Token Generator. It signs you in with your ezeep account and returns a refresh token for the sandbox client below, which you exchange for access tokens.

Public ClientID, Redirect URI for First Tests with this Documentation

The sandbox client below is for testing only. You can use it for authorization and Print API requests while you try out the API. For a production integration, use your own client ID (see Managing OAuth Clients).

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”