Recent changes

Monday, 2017-03-13

Dear users,

We have an important announcement to make that affects all applications using the Upwork API.

Our team is going to deprecate the List team rooms and Get team room API. We suggest you make the necessary changes in your application code to anticipate to the upcoming modifications.

Thank you, The Upwork API team

Monday, 2016-11-21

Dear users,

We have an important announcement to make that affects all applications using the Upwork API.

Our team is going to deprecate the parameter test from the Post Job API. We suggest you make the necessary changes in your application code to anticipate to the upcoming modifications.

Thank you, The Upwork API team

Sunday, 2016-11-20

Dear users,

We have an important announcement to make that will affect all applications that use the Upwork API.

Our team is going to upgrade Applications API from v3 to v4. As a result, we are going to deprecate the old APIs after December 11st. Thus, we strongly recommend you update your software accordingly.

If you have any questions or concerns, do not hesitate to email us at apisupport@upwork.com.

Thank you, The Upwork API team

Friday, 2016-10-21

Dear users,

We have an important announcement to make that will affect all applications that use the Upwork API.

Our team is going to deprecate the parameter context[job_application_ref] and replace it with the new parameter context[cj_job_application_uid]. The proper value you can find in the response of List engagements or Get engagement API.

Starting November 4th, Send client offer will return an exception if the parameter context[job_application_ref] is specified in the request.

If you have any questions or concerns, do not hesitate to email us at apisupport@upwork.com.

Thank you, The Upwork API team

Thursday, 2016-06-02

Dear users,

We have an important announcement to make that will affect all applications that use the Upwork API.

Our team is always looking for ways to enhance the Upwork API and to provide a better user experience. To that end, today we introduce a new API resource:

Starting August 1th, Messages API will be deprecated and we will stop returning data for it. Please, proceed with applying the necessary changes in your application code to comply with the upcoming changes.

If you have any questions or concerns, do not hesitate to email us at apisupport@upwork.com.

Thank you, The Upwork API team

Monday, 2016-05-09

Dear users,

We have an important announcement to make that will affect all applications that use the Upwork API.

We stop returning the fields dev_bill_rate and hourly_pay_rate in all Upwork API calls. Please, make sure you perform the necessary changes in your application code to comply with the upcoming changes.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Tueday, 2016-04-12

Dear users,

We have an important announcement to make that will affect all applications that use the Upwork API.

By the beginning of May, we will stop returning the fields earnings, earnings_online and earnings_offline in all Reports API calls. Please, make sure you perform the necessary changes in your application code to comply with the upcoming changes.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Saturday, 2016-04-08

Dear users,

We have an important announcement to make that will affect all applications that use the Upwork API.

By the beginning of May, we will stop returning the fields fixed_pay_amount_agreed, weekly_salary_charge_amount and fees_percent in all Contracts and Offers API calls. Please, make sure you perform the necessary changes in your application code to comply with the upcoming changes.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Tuesday, 2015-11-24

Dear users,

We have an important announcement to make that will affect all applications that use the Upwork APIs.

Starting Dec 9th, we will stop returning data for tickets threads in Messages API. Please proceed with applying required changes in your application code to comply with the upcoming changes.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Thursday, 2015-10-12

Dear users,

Our team is always looking for ways to enhance the Upwork API and to provide a better user experience. To that end, today we introduce a new API resource:

All our libraries were updated accordingly.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Thursday, 2015-08-12

Dear users,

We are glad to introduce a new library - GO bindings for Upwork API.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Thursday, 2015-07-31

Dear users,

We are glad to introduce a new library - Perl bindings for Upwork API.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Thursday, 2015-07-16

Dear users,

Our team is always looking for ways to enhance the Upwork API and to provide a better user experience. To that end, today we introduce two new API resources:

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Friday, 2015-06-05

Dear users,

A month ago, we announced important changes that would affect all the applications that use Upwork API.

This announcement serves as the last notification before we deprecate our old oDesk domain. After June 15 2015, we will start redirecting all requests to upwork.com.

Please, to avoid any disruptions:
  • • Replace all X-Odesk- headers with X-Upwork-
  • • You may also need to update public libraries - please check Libraries and Tools for more details

We recommend making these modifications to the affected code and set up future implementations using the Upwork domain.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Tuesday, 2015-05-05

Dear users,

We have an important announcement that affects all applications that use oDesk APIs.

As you may already know, the oDesk.com domain has been replaced by Upwork.com. Therefore, in 4 weeks we will start redirecting all oDesk API requests to the new Upwork domain.

As a consequence of the forwarding process, all POST/PUT/DELETE requests made to odesk.com will stop working correctly.

To avoid any disruptions:
  • • Replace all X-Odesk- headers with X-Upwork-
  • • You may also need to update public libraries - please check Libraries and Tools for more details

We recommend making these modifications to the affected code and set up future implementations using the Upwork domain.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2015-03-21

Dear users,

Almost two months ago we suggested you start updating your software to prepare it for the migration to the List categories V2 API resource. Today, we would like to notify that the List categories resource and all parameters related to it in other resources will be depricated after April 15, 2015. We suggest you start making the necessary modifications to the code that might be affected and consider this change in your future implementations.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2015-03-20

Dear users,

In an on-going effort to meet our users’ needs we have recently implemented the possibility to get, update and delete a Snapshot by specific Contract ID. You can check out all the technical details in our documentation for Get snapshot by Contract API, Update snapshot memo by Contract API and Delete snapshot by Contract

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2015-03-03

Dear users,

In an on-going effort to meet our users’ needs we have recently implemented the possibility to accept and decline offers. You can check out all the technical details in our documentation for Accept or decline an offer API.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2015-02-17

Dear users,

There are some changes coming soon to the Post job API resource that may need your attention. We will be adding a new conditionally required parameter called category2. This parameter will accept values from the List categories V2 API resource. We suggest you start making the necessary modifications to the code that might be affected and consider this change in your future implementations.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2015-02-12

Dear users,

The API call will return an error message whenever the user has concurrent contracts, that is to say, he/she works on more than one contract at the same time. Now, to avoid getting the error mentioned, you can use a new resource called Get Work Diary by Contract.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2015-01-28

Dear users,

There are some changes coming soon to the Search for Freelancers and Search for jobs API calls that may need your attention. In consonance with the new structure of categories, our next release will support two new parameters: category2 and subcategory2. The list of valid values for these parameters will be available via a new API call List categories V2 API. This resource allows getting categories according to the new structure. We are also going to add a new conditionally required parameter called subcategory2 to the Post job API resource. Moreover, the parameters category and subcategory will also become conditionally required. Therefore, the API call will require either Category V1 or Category V2 (if both specified, V2 will have priority over V1).

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2015-01-24

Dear users,

There are some changes coming soon to the End Contract API call that may need your attention. After February 27th 2015, this call will require a new parameter called fb_private which describes private feedback given to a freelancer. This parameter will accept an integer value from 1 to 11.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2015-01-12

Dear users,

There are some changes coming soon to the Send client offer API call that may need your attention. After February 6th 2015, the charge_upfront_percent and expires_on parameters will be deprecated and will be ignored if they still exist in your requests. Moreover, the milestone parameter will become required. We suggest you start making the necessary modifications to the code that might be affected by these changes and consider them in your future implementations.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2014-12-10

Dear users,

In an on-going effort to meet our users’ needs we have recently implemented the possibility to set internal milestones in fixed-price contracts. As part of this implementation we have also developed a set of resources to manage these milestones.

These new calls allow you to:

You can check out all the technical details in our API reference.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Wednesday, 2014-12-03

Dear users,

There are some changes coming soon to the Make custom payment API call that may need your attention. After January 14th 2015, the amount parameter will be deprecated and will be ignored in case it still exists in your requests. Moreover, the charge_amount parameter will become required. We suggest you start making the necessary modifications to the code that might be affected by these changes and consider them in your future implementations.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Friday, 2014-11-21

We have recently implemented changes to the Post Job and Update Job API calls that may need your attention. The end_date parameter has been deprecated and will be ignored in case it still exists in your requests.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Friday, 2014-10-31

Dear users,

Our team is always looking for ways to enhance the Upwork API and to provide a better user experience. To that end, today we are releasing a change in our Send Client Offer API.

We introduce the related_jobcategory as an optional parameter to be passed in the Send Client Offer API. You can pass the category related to your job in two different ways. Either by directly using the related_jobcategory parameter or by using context[related_jobcategory]. You can find the list of available categories in our List categories API.

Please note that for now the job category is introduced as an optional parameter. Although we plan on making it a required one in a month. We would really appreciate it if you could start migrating your clients code to define the job category parameter in one of the two ways indicated above.

Please do not hesitate to email us at apisupport@upwork.com with any questions or concerns.

Thank you, The Upwork API team

Friday, 2014-09-26

We are introducing two new calls for the Contracts and Offers API:

The Archive activities and Unarchive activities calls now support multiple activity codes, semicolon-separated, check it out.

Thank you, The Upwork API team

Friday, 2014-08-15

A number of API changes were made in order to move forward our deprecation policy and also two new calls were introduced in the Messages resources:

Removed documentation for the following calls:

If you have any questions or requests regarding these latest changes, please feel free to email us at apisupport@upwork.com.

Thank you, The Upwork API team

Friday, 2014-08-08

Dear users,

Our team is always looking for ways to enhance the oDesk API and to provide a better user experience. To that end, today we are releasing a new documentation site and improvements on a number of API resources.

The new documentation site is now powered by an infrastructure which provides a friendly and faster experience. Also, we made a number of usability changes to help you easily navigate through the API resources we offer. Along the benefits of our new API documentation site, now you will be able to find code examples to invoke relevant API calls using our newly released clients, in various languages, namely:

We are also releasing today a number of changes for the old oTasks resource:

  • • Due to the migration from the old oTasks resources to the new Activity codes, now the oTasks resources section is called “Activities”. Note that “activity” is the term we use in the up-to-date documentation exclusively when we refer to a “task”.

  • • User-level API calls for Activities (former oTask) were removed. Now all the activities belong to the team level and can be assigned to a freelancer’s engagement. This change allows the client to access detailed financial reports on specific activities. Learn more about these options at the Activities section.

  • • The new API calls for managing activities are:

  • • Calls for deleting activities are considered deprecated. We strongly encourage you to use archive/unarchive calls.

If you have any questions or requests regarding these latest changes, please feel free to email us at apisupport@upwork.com.

Thank you, The Upwork API team

Wednesday, 2014-02-26

Dear users,

In Dec. 2013 we announced that our APIs will be undergoing a major cleanup, and part of this cleanup would be the removal of redundant fields from our responses in various APIs. Today we are glad to announce that the last APIs to be cleaned up (Provider Profile and Job Profile) have been released and with this we conclude this major effort.

We appreciate your understanding during this time and we welcome your feedback.

If you have any questions/requests for those changes please feel free to email us at apisupport@upwork.com.

Thank you, The Upwork API team

Thursday, 2014-02-20

Dear users,

A while ago we had announced the revamp of our available Offer APIs. These APIs were used to fetch both offers and applications for a job.

In the first phase of our changes we made sure to expose the new Client Offers and Freelancer Offers APIs, which you can use to Get and List Offers as a Client or a Freelancer and Make an Offer as a Client.

Today we are glad to announce a new set of APIs, the Client Job Applications and Freelancer Job Application. These new APIs will allow our users to GET and List Job Applications as a Client or a Freelancer. They include a number of new handy capabilities, like the ability to filter by status of the job application.

You will need to update your integration to the new APIs by April 11th, 2014. So that we can best help you transition to the new APIs, we ask that you take a look at your interfaces and test out integrations using the new APIs as soon as you can. Support for the old APIs will no longer be available after the end of April.

Please reach out to us at apisupport@upwork.com with any questions/concerns.

Happy working, the Upwork Crew

Monday, 2014-01-20

Dear users,

Few months ago we announced a new version (v2) for the freelancers and jobs search APIs. These new APIs have been developed and improved over the last few months with your valuable input.

Today we announce that the legacy v1 search APIs are discontinued. To avoid an interruption of your service, if you use the v1 APIs, we recommend you replace them the soonest possible.

If you have any questions/requests/suggestions for the new search APIs please feel free to email us at apisupport@upwork.com.

We really appreciate your understanding and request that you react to this in a timely manner.

Thank you, The Upwork API team

Wednesday, 2013-12-04

Dear users,

In the following few months we are planning on releasing few changes that are going to affect few of you.

Internally we are undergoing a major clean-up of our source code. Part of this cleanup includes removing redundant fields from our responses in various APIs. In majority of those cases these changes are not going to affect you, although in some cases changes from your end may be required.

In this release we have also updated Client Offers to make it easier - company reference is not required any more as a part of router, and API is able to infer the company from the call context. Please check list of parameter in the documentation.

If you have any questions/requests for those changes please feel free to email us at apisupport@upwork.com.

We really appreciate your understanding.

Thank you, The Upwork API team

Thursday, 2013-11-14

Dear users,

Our team is always looking for ways to enhance the Upwork APIs and to provide a better user experience. To that end, in the following few months we are planning on releasing few changes that is going to affect few of you.

Internally we are undergoing a major clean up of our source code. Part of this cleanup includes removing redundant fields from our responses in various APIs. In the majority of those cases these changes are not really going to affect you, although in some cases changes from your end may be required.

We will make sure we provide extensive documentation on what is removed/replaced to make the transition as smooth as possible from your end.

With that said, today we announce the first APIs affected by this cleanup. Those are:

  • • Search Jobs V1
  • • Search Providers V1

Also, today we announce one new API that should help you avoiding unnecessary hardcoding in your code and automate lists of Reasons required in some cases as parameter.

The new API is called Reasons API and is available as a part of Metadata APIs.

If you have any questions/requests for those changes please feel free to email us at apisupport@upwork.com.

We really appreciate your understanding.

Thank you, The Upwork API team

Thursday, 2013-10-31

Dear users,

We have revamped the available Offer APIs. They include a number of new handy capabilities, like the ability to send job offers with some basic job details without having to post a job first.

You will need to update your integration to the new APIs (including any integration using get Offers, get Specific Offer, and Make an Offer) by December 1st, 2013. So that we can best help you transition to the new APIs, we ask that you take a look at your interfaces and test out integrations using the new APIs as soon as you can. Support for the old APIs will no longer be available after December 1st.

Please reach out to us at apisupport@upwork.com with any questions/concerns.

Happy working, the Upwork Crew

Friday, 2013-10-25

Dear users,

Our team is always looking for ways to enhance the Upwork APIs and to provide a better user experience. To that end, we’re announcing today a new version (v2) for the freelancers and jobs search APIs.

These new APIs have been updated to include functionality frequently requested by our users. Additionally, we have reduced the response size of the APIs and made improvements to our backend to deliver improved speed.

To avoid an interruption of your service we recommend you replace the v1 search usage in your application with the v2 version. There is extensive documentation on this here: freelancers, jobs.

We plan to discontinue support for v1 search by the end of the year, so we strongly encourage you to proceed with the migration as soon as possible.

If you have any questions/requests for the new search APIs please feel free to email us at apisupport@upwork.com.

We really appreciate your understanding and request that you react to this in a timely manner.

Thank you, The Upwork API team

Monday, 2013-10-07

Dear users,

The Upwork API team is always looking for ways to protect API users. To that end, we’re deprecating the token authentication mechanism (aka API Keys) for all the APIs.

At this point only a small percentage of the keys that have been actively used within the last year are legacy (token) ones.

We kindly request from you to proceed with replacing the API Keys usage in your application with the well-known and supported OAuth mechanism. See the Authentication section.

To identify if you are using legacy vs OAuth keys, please visit this page here: https://www.upwork.com/services/api/keys and look for the “Auth type” https://url.upwork.com/q2vl1q of your key. If the “Auth type” is API Keys then your application is vulnerable and you need to replace your implementation of authentication with the OAuth one.

We will continue to evaluate the impact of this change before setting a date for dropping the support altogether, and we’ll share that date as soon as we know it.

If you have any questions please feel free to email us at apisupport@upwork.com.

Monday, 2013-09-02

Please pay attention, starting from today “owner_user_id” field in response from Organization APIs is replaced with “owner_ciphertext” for security reasons.

Thursday, 2013-08-22

Please pay attention, starting from today oConomy Reports API is deprecated and won’t return any data.

Thursday, 2013-06-06

Search Providers API started to support a new parameter called skills.

Wednesday, 2013-06-05

A new rebranded design for API Center has been released. Search Providers API was updated to support multiple parameter for specifying a couple subcategories.

Wednesday, 2013-04-03

List Offers API started to support a new parameter called ‘profile_key’, which is an alias to provider__reference, and will help to avoid making additional calls in some circumstances to get a reference.

Thursday, 2013-03-28

Upwork is glad to announce that from now you are able to setup permissions which your application require. Using Application Permissions feature let your application be flexible and trustworthy.

Thursday, 2012-11-15

Real PUT/DELETE methods have become available for JSON requests, read more about their usage

Wednesday, 2012-11-14

Upwork made a redirect for login form (from www.upwork.com/login.php to www.upwork.com/login) last Wednesday. Please take an attention on this change, it may affect your applications in case your library doesn’t support redirects. We’ve update our example php libraries as well.

Monday, 2012-10-29

Update Job API has been updated - job_type parameter is deprecated, there is no possibility to change the type of a Job.

Thursday, 2012-09-27

Update Job API has been updated - job_type parameter has become optional.

Thursday, 2012-05-31

Search Jobs API has been updated - a new parameter has been added to allow filter by skill.

Thursday, 2012-01-19

We’ve run a new powerful feature for control permissions of any application key in close mode; it means that from now developers are able to setup/limit permissions those are required for theirs applications, at the same time any user who authorizes app will see a proper message with descriptions which rights requires this app.

If you want to try/use this feature you need to contact us by email with subject “extended api permissions” and provide your userid in email.

Thursday, 2012-01-12

A new Metadata API has been released.

Tuesday, 2011-12-27

Due to update of Search Jobs API a parameter “dp” will be changed starting from 01.11.2012 and will work in the same way as on GUI. The new supported values: 0 for Last 24 Hours, 1 for Last 3 Days, 3 for Last 7 Days, 7 for Last 14 Days, 14 for Last 30 Days. Please, prepare your applications for future update.

Monday, 2011-12-19

A new Job Profile API available, it allows you to get detailed Job Profile info.

Wednesday, 2011-12-07

Make Offer API and Post a Job API now support simple parameters without need to wrap them into array. Make Offer API has a new parameter - keep_open.

Wednesday, 2011-11-30

Update batch from oTasks API was fixed and available.

Thursday, 2011-11-17

Invite to Interview API now has a new parameter provider__reference. Make Offer list of parameters was fixed in documentation, API supports now profile_key of provider.

Wednesday, 2011-11-02

A new “My Info” API available. Organization APIs API for getting authed user info extended with profile_key.

Wednesday, 2011-10-12

Offers API updated, “Make Offer” API now accepts profile_key, if no provider’s reference available. Jobs HR API updated, added “Invite to interview” API. “End Contract” API became available .

Wednesday, 2011-09-14

Per requests we decided to switch on a possibility of creating API Keys for all users (it means including new developers), note that this will be deprecated in future (we will notify TM).

Friday, 2011-09-09

Great news: we released an OAuth 1.0 protocol for public usage Sad news: we deprecated API Keys. It means:

  • • The documentation was moved under section “Archived”
  • • We continue to support old (already created) keys
  • • But you can’t create new key (type “API Keys”) any more
  • • All new keys will be created for working with OAuth 1.0 only

Thursday, 2011-08-25

Updated Java Library to version 0.1.1, fixed error with encoding of parameters when calculating signature Added new API for making offer.

Wednesday, 2011-06-15

Added support of authentication by headers for OAuth.

Monday, 2011-05-30

API Libraries was updated: added link to new “python-odesk” library

Wednesday, 2011-05-11

Fixed issue in oConomy Reports API: empty response for months 2011-03, 2011-04 and 2011-05.

Friday, 2011-05-06

Important note: Provider Profile API will fully deprecate support of field “dev_usr_score” in release 5/18. Please update your applications accordingly.

Friday, 2011-04-15

New router for getting info about current authenticated user shared under Organization API.

Monday, 2011-04-04

Important note: search providers API will deprecate support of sorting keys in release 4/13. Please update your applications accordingly.

Wednesday, 2011-03-23

OAuth authentication method available (currently in its beta testing phase and is available on request only, if you are interested in participating to the OAuth beta, Please contact our API support team including your Upwork username and we will send instructions about the next steps.

Wednesday, 2011-02-09

New simplified login screen for mobile devices (detected automatically) is shared . New simplified authorization screen becomes available for smartphone devices (detected automatically).

Wednesday, 2010-12-15

Fixed interconnection issue in Team API (wordiary_api and snapshot_api).

Wednesday, 2010-12-8

A new GDS API available for usage - oConomy Reports API.

Monday, 2010-11-01

Important: take an attention, starting from release 10/11 we remove some fields from the response in search providers and search jobs, also the same fields will be removed from Provider Profile. The full list of deactivated fields: providers - “op_buyer_ace”, “op_cny_url”, “op_company_id”, “op_company_name”, “op_tot_hr_charge”, “op_tot_fp_charge”, “trends”; jobs - “dev_full_name”, “trends”, “ag_teamid”, “ag_teamid_rollup”. Providing an access to the above fields was a mistake. We can no longer support them. Please, update your applications accordingly.

Wednesday, 2010-10-06

Please, take an attention, that with release 6/10 we fix an issue in structure of userroles response and return old one. Parameter ?include_user_info=0 is still available and allows you to exclude tag “user” from response, which is included by default.

Wednesday, 2010-09-29

For User Roles request added new parameter ?include_user_info=0|1. Using ?include_user_info=1 allows to have additional user info in response. User Roles response structure is changed, if you require old structure please use parameter ?include_user_info=0 together with request.

Wednesday, 2010-09-15

The /api/team/v1/teamrooms router moved from version (v1) to (v2), e.g. /api/team/v2/teamrooms. More info - Team API . Please update your application accordingly.

Tuesday, 2010-07-27

The Upwork PHP library has been updated to version 0.3 and supports a variety of environments and options. The PHP library examples have been updated and a new non-web example has been added.

Thursday, 2010-07-22

Changes to the freelancer (provider) search API.

Monday, 2010-07-12

Changes to the Jobs Search API. New Ruby on Rails library and a simple example using it.

Friday, 2010-07-02

New cross domain file allows access by Flash clients.

Monday, 2010-06-28

Your applications can now post, update or delete jobs via the API. This is a major update so check out the new Jobs API section.

Friday, 2010-05-28

The financial reporting API allows you to generate custom financial reports based on your Upwork financial account.

A custom payments API allows you to generate custom (or bonus) payments to your providers.

One of the biggest updates in the past months has been the hiring APIs, a lot of new ways to query your account on Upwork, get job details, provider details and more.

To go along with the hiring APIs we have the organization APIs to give you more info on your teams and companies, get team members and a lot more.

Our API libraries have gotten a few significant updates recently, we now have Ruby and Java APIs that should help developers get up to speed and make working with the APIs even easier.

Tuesday, 2009-12-29

We now have a complete Upwork API library to help speed up development time. There are also several new examples using our library as well as a detailed walkthrough of how the library works.

Tuesday, 2009-11-03

The Examples page has been updated with detailed PHP code for authenticating a web application and processing Message Center API requests.

Monday, 2009-11-02

Message Center APIs released. Third party applications now have full access to the Upwork Message Center. Send, receive and check messages in the Upwork Message Center.

Friday, 2009-10-30

Updated the Time Reports API. Updated the Authentication API.

Wednesday, 2009-10-28

We now have a community IRC channel: #odesk running on freenode.net, so drop by and say hi:)

Wednesday, 2009-10-21

Now you can custom reports for teams, providers, companies and agencies with the Upwork Time Reports API.

Saturday, 2009-10-09

Job Search API & oTask API are released.

Search and display jobs via the API.

Synch your third party bug and task tracking software with the Upwork oTask API.