Upwork API Automation Toolkit for Freelancers
Automate and streamline your Upwork freelancer workflow using the Upwork API directly from the terminal.
Upwork API Automation Toolkit for Freelancers
This Python package helps Upwork freelancers automate their daily workflows using the official Upwork API. It is designed to boost efficiency and reduce manual effort by providing programmable access to common tasks and events on the platform.
Features:
- Fetch and display public reviews from your Upwork profile for your personal portfolio
- Set up real-time alerts for:
- New messages from clients with active contracts
- Invitations to interview
- General inbox messages
- Periodically scan job posts using custom filter logic and notify you with relevant links
- Retrieve and monitor personal data such as:
- Earnings
- Work diary
- Automate common actions via the command line
Whether you're an experienced freelancer or just starting out, this tool helps you stay responsive, informed, and efficient — all while remaining compliant with Upwork’s terms of service.
Setup Requirement
- Get an API Key from upwork https://www.upwork.com/developer/keys/apply
- Set an environment variable
export UPWORK_API_KEY=<your-upwork-api-key> - Set an environment variable
export UPWORK_API_SECRET=<your-upwork-api-secret> - Install this package from pypi
pip install upwork-cli
Usage
upwork-cli or upcli can be used to run this tool from terminal.
use upcli --help to view the available options and commands.
🧪 Project Structure
📁 upwork-cli/ ├── 📁 src/ │ └── 📁 upwork_cli/ │ ├── __init__.py │ ├── __main__.py │ ├── __init__.py ├── 📁 examples/ │ └── sample_usage.py ├── 📁 tests/ │ └── test.py ├── ⚙️ .env ├── 🚫 .gitignore ├── 📃 LICENSE ├── 📃 LICENSE.txt ├── ⚙️ pyproject.toml ├── 📝 README.md └── ⚙️ ruff.toml
📄 License
Licensed under the MIT License.
🤝 Contributing
- Open an issue for ideas, bugs, or suggestions.
- Pull requests are welcome!
🔗 Links
- 📦 PyPI
- 🛠️ Issues
- ⭐ Star on GitHub
Metadata
Release files for upwork-cli 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| upwork_cli-0.1.0.tar.gz | 61.9 kB | Without provenance | Details for upwork_cli-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| upwork_cli-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for upwork_cli-0.1.0-py3-none-any.whl |
Total release size: 73.7 kB
Release files / upwork_cli-0.1.0.tar.gz
| Download URL | upwork_cli-0.1.0.tar.gz |
|---|---|
| Size | 61.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31a536b2ae74dd6c10c55ac5728189ffbfc91f7a3a646dd0d250d0c691dd4e82
|
|
BLAKE2b-256 checksum How to use checksums |
7fb91787fe28c45054a494db58aecb4ca65d9ba69684e12cf9b0208bc45aeb38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.6
|
Release files / upwork_cli-0.1.0-py3-none-any.whl
| Download URL | upwork_cli-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9dca7577d81e513d8690d4338029e60dc248c74571edefc3f81c87d315d35b11
|
|
BLAKE2b-256 checksum How to use checksums |
f9783d995ccf2d26eaa3a96a16bcaca62332d288ed244c90cd79ef15a97dca4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.6
|
Security for upwork-cli 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.