Upwork automation policy

Upwork's help article sets the scope widely: any script, program, browser extension or third-party service that automatically sends requests to Upwork, collects data, or performs actions "faster or more frequently than a human could". A tool that says it was made for Upwork is not thereby approved, and Upwork says it makes no exceptions for productivity tools.

The permitted route is the API. Upwork's answer for anyone who wants to automate part of a workflow is to request an Upwork API key; the review looks at both the account and the stated use case. A key does not authorise everything. Spamming proposals or invites and scraping public or private data stay off-limits, and Upwork lists reasons keyed accounts still get flagged:

• using OAuth tokens or session cookies from a browser or official client in a script;
• calling website pages instead of approved API endpoints;
• mixing an API key with exported browser or session tokens;
• exceeding rate limits, or background polling that resembles scraping;
• using a key outside its scope, or sharing keys across users without authorisation.

The full terms sit in the API section of Upwork's Terms of Service.

Extensions count. Upwork warns that job watchers, auto-refresh tools, page monitors, macro recorders, user-script managers, infinite-scroll helpers and anything that sends requests while the tab is idle can trigger enforcement, even for someone who believes they automate nothing; see browser extension.

Enforcement. Detection is automatic. Unapproved automation leads to a temporary restriction or a permanent block, depending on severity and repetition, and using a key outside its scope can end API access.