① Configure your connection
MOCK MODEEnter your eWarp API credentials — your username + password are your API key. They fill every request below and are kept only for the current browser session — your credentials are cleared as soon as you close the browser and are never sent anywhere except the eWarp API. In Mock mode the console returns documented example responses, so you can explore without credentials. Switch to Live mode to call the selected environment for real and get the actual response.
Paste a header to fill username and password.
⚠️ Live mode sends your real credentials to the selected environment and returns the
actual response. Requests go directly from your browser — if the API blocks cross-origin (CORS)
calls, use Copy as cURL and run it from your terminal instead.
How the Authorization header works
Every request sends a static API key in the Authorization header. The fields above build it for you.
Authorization: EWS <username>:<base64(password)>| Field | Description |
|---|---|
EWS | Realm — fixed literal |
username | eWarp username provided by Esoft |
base64(password) | The password base64-encoded (not hashed). Static key — no OAuth, no refresh. |
Common mistake: Hashing the password (MD5/SHA) instead of base64-encoding it causes persistent
401 errors. Base64 is an encoding, not a hash — the original password is recoverable from it.