The Zeplo CLI helps you to view requests, manage your account and includes a
Install using NPM:
Install using script:
You should update Zeplo by running the same command.
For additional usage commands use
-h on sub-commands. E.g.
zeplo workspaces -h.
Dev Server (
A local dev server that can be used during development. It implements the same API as the
zeplo.to. By default it runs on http://localhost:4747 - you can specify an alternative port using
To start a dev server use:
And to queue a request use:
requests commands support a
--dev flag which can be used to target your dev server instead of the Zeplo production servers. E.g. To list requests on your dev server use
zeplo requests --dev
You can specify a workspace ID (and optional token) when creating the dev server, this allows you to start multiple servers without causing conflicts.
There are some minor differences to the production server:
If token is not provided using
zeplo dev -w name:token, then _token is not required. In production, _token param is always required.
Only the the following endpoints are supported. These endpoints work in the same way as the Zeplo API, unless otherwise specified:
- Queue [ANY] -
http://localhost:4747/<url>(incl all headers/query parameters)
- Bulk [POST] -
- List requests [GET] -
http://localhost:4747/requests. Only exact match filters are supported (e.g.
- Get a single request [GET] -
- Pause request [PATCH] -
- Unpause request [PATCH] -
- Get request body [GET] -
- Get response body [GET] -
- Queue [ANY] -
In addition, you can reset/remove completed requests by calling
/requests/reset[POST]. If you wish to remove ALL requests (including pending and active requests), then append
?hard=1. This can be useful for automated testing.