Authorization

Just want to try out the API? Use the API Token Generator to get a ready-to-use refresh token for the demo Client ID in minutes - without implementing any of the OAuth flows below.

All API requests require authentication via a bearer OAuth2 token. These tokens can be obtained from the ezeep Authentication Service. This service implements the following Authorization Flows:

OAuth 2 Tokens

You can use an OAuth 2 access token to authenticate with the API by passing it in the Authorization header.

Example of using the OAuth2 token in the header:

curl --header "Authorization: Bearer eyJ..." https://printapi.ezeep.com/sfapi/GetPrinter/

Note: All OAuth access tokens are valid for one hour after they are created.

All APIs use JSON for data serialization unless otherwise specified.

Obtaining a ClientID for your Application

Be sure to keep the customer secret secure and never share it, especially in components that you will pass to others. If it is necessary to embed the client secret in the application, you may be using an incorrect authentication method.

Organization administrators can create a Client ID and optional Client Secret themselves, via the Managing OAuth clients REST API or, for public PKCE clients, the MCP self-service prompt. Please also register your redirect URI(s) with the client. The redirect URI(s) is where the user will be redirected to after they have granted permissions to your application. This is typically a URL on your server where you can handle the authorization code or access token. Only with this final redirection the code needed for getting the access_token and optionally a refresh_token will be provided.