Upwork freelancers that work as developers are provided with access to our web services. They can build their own application and integrate Upwork features and workflow in their web based or mobile apps.
API key requests or questions about APIs should always be routed to the Special Projects queue. Any team other than Special Projects, when you receive these requests, send a public touch response first, then please apply the macro API to Special Projects. No further action is needed.
API Key Requests
Please follow the process using Public API Approval Process document.
Refer to the table below for the rejection reasons with corresponding ZD macros to use.
| Tool | Checkpoint | Criteria to reject | ZD Macro Title |
| 1. API Request - Title | Title - No Upwork |
|
In process |
| 2. API Request - Description |
- A clear description on what you plan to use our API for - The purpose of your project - Whether you use the application internally or publicly |
|
In process |
| 3. OBO - Username | valid username (no company names (company name PNV) or fake names are allowed) | 1. Without valid username (no company names (company name PNV) or fake names are allowed) | In process |
| 4. OBO - Address |
full valid address either address in personal profile or company’s address must be provided sometimes users omit apartment, or specify only street - those are not valid cases |
|
In process |
| 5. OBO - Profile Portrait | profile portrait | 1. Without valid Portrait | In process |
| 6. OBO - Suspension | Check if user is suspended | 1. Suspended | In process |
| 7. OBO - Earnings | >30,000 | 1. <30,000 | In process |
For issues with API, please refer to the Special Project Agent Tools below:
If you are unable to solve the API issue after using the tools, please send a public touch response first, then escalate using the API to Tech Support macro.