ÃÛ¶¹ÊÓƵ

DocumentationWorkfrontWorkfront Guide

HTTP request methods in ÃÛ¶¹ÊÓƵ Workfront Fusion

Last update: Tue Jan 24 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User

When you are configuring an API call in a module, you need to fill in the field for the HTTP request method.

Access requirements

You must have the following access to use the functionality in this article:

ÃÛ¶¹ÊÓƵ Workfront plan*
Pro or higher
ÃÛ¶¹ÊÓƵ Workfront license*
Plan, Work
ÃÛ¶¹ÊÓƵ Workfront Fusion license**

Current license requirement: No Workfront Fusion license requirement.

Or

Legacy license requirement: Workfront Fusion for Work Automation and Integration

Product

Current product requirement: If you have the Select or Prime ÃÛ¶¹ÊÓƵ Workfront Plan, your organization must purchase ÃÛ¶¹ÊÓƵ Workfront Fusion as well as ÃÛ¶¹ÊÓƵ Workfront to use functionality described in this article. Workfront Fusion is included in the Ultimate Workfront plan.

Or

Legacy product requirement: Your organization must purchase ÃÛ¶¹ÊÓƵ Workfront Fusion as well as ÃÛ¶¹ÊÓƵ Workfront to use functionality described in this article.

To find out what plan, license type, or access you have, contact your Workfront administrator.

For information on ÃÛ¶¹ÊÓƵ Workfront Fusion licenses, see ÃÛ¶¹ÊÓƵ Workfront Fusion licenses.

HTTP methods

Use one of the following HTTP methods.

  • GET: Retrieves data from a web server based on your parameters. GET requests a representation of the specified resource, and receives a 200 OK response message with the requested content if successful.
  • POST: Sends data to a web server based on your parameters. POST requests include actions like uploading a file. Multiple POSTs may result in a different outcome than a single POST, so be cautious about unintentionally sending multiple POSTs. If a POST is successful, you receive a 200 OK response message.
  • PUT: Sends data to a location in the web server based on your parameters. PUT requests include actions like uploading a file. The difference between a PUT and POST is that PUT is idempotent, meaning that the result of a single successful PUT is the same as many identical PUTs. If a PUT is successful, you receive a 200 response message (usually 201 or 204).
  • PATCH: (Not available for some API call modules) Applies partial modifications to a resource on a web server based on your parameters. PATCH is not idempotent, meaning that the result of multiple PATCH’s could have unintended consequences. If a PATCH is successful, you will receive a 200 response message (usually 204).
  • DELETE: Deletes the specified resource from the web server based on your parameters (if the resource exists). If a DELETE is successful, you receive a 200 OK response message.
recommendation-more-help
5f00cc6b-2202-40d6-bcd0-3ee0c2316b43