Start making calls to the ezeep API in
minutes — no OAuth implementation required.
How it works:
Sign in with your ezeep account below. You receive a long‑lived refresh token, issued
for a shared public demo Client ID and tied to your account.
Store the refresh token in your application as a secret credential — like a password:
keep it in an environment variable or secret store, never in client‑side code or a public repository.
Whenever your application needs to call the API, it exchanges the refresh token for a short‑lived
access token (a JWT, valid for about one hour) and sends that with each request as a
Bearer token.
No token rotation: refresh token rotation is switched off for this Client ID. The refresh
token you generate here stays valid until it is revoked, and the same token can be exchanged for new access
tokens any number of times — your application never needs to update the stored value.
Step 1: Sign in with your ezeep account
The ezeep login page will open in a new tab. Complete the sign‑in there, then return here. The
authorization must be completed within 10 minutes.
Instructions: Complete the ezeep login process in the new tab, then return here.
Step 2: Receive your refresh token
This page detects automatically when you have finished signing in and then shows your refresh token together
with everything you need for your first API call.