In this article

Overview

We recommend that you use the HTTP Client Snap instead of Snaps from the REST Snap Pack to connect to REST-based APIs and applications.

You can use the REST Put Snap to replace business object resources. If the business object does not exist, the Snap creates the object.

Prerequisites

A valid account with the required permissions.

Supported Features

Works in Ultra Tasks. We recommend you to set the batch size to 1.

Limitations and Known Issues

None.

Snap Views

Views

View Type

View Format

Examples of Upstream and Downstream Snaps

Description

Input

Document

Min: 0
Max: 1

Mapper
Script
Router

Each input document contains details associated with the data that must be replaced or created in the target RESTful server.

Output

Document

Min: 0
Max: 1

JSON Splitter
JSON Formatter
Join

Each output document contains details related to the business objects impacted as a result of Snap execution.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:

Stop Pipeline Execution: Stops the current pipeline execution when the Snap encounters an error.
Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.
Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

Field Name	Field Type	Description
Label* Default Value: REST Put Example: REST Put	String	Specify a name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.
Service URL*	String/Expression	Specify the service endpoint URL of REST API. You can provide the URL in one of the following ways: As a JavaScript expression in the expression language. For example: `http://coresnapsqa-v4.s3.us-east-2.amazonaws.com/S3Account/'+encodeURIComponent("Special_char_owner_!3)12.json")` As a plain string that you should enclose in double quotes (""). For example: `"https://www.example.com/slm/webservice/v2.0/defect/%s".replace("%s", $.widg et.id)` For Snaps using AWS Signature V4 accounts, you can use the canonical name (CNAME) for the URI so it's not necessary for the URL to end with amazonaws.com or have the region and service provided in it. However, if you are using the CNAME you must provide it in the AWS Region and Service Name fields in the AWS Signature V4 account. The host name in the CNAME must be equal to the bucket name. For example: Previous URI: `https://jsmith-bucket.nia3.snaplogic.net.s3.us-west-1.amazonaws.com/HttpClientTest/test1` New URI with CNAME: `https://jsmith-sltest.nia3.snaplogic.net/HttpClientTest/test1` Here, the bucket name is `jsmith-bucket.nia3.snaplogic.net` The Snap finds the value at the JSON path $.widget.id in the input data and replaces "%s" in the Service URL with the value. You can connect File Reader and JSON Parser Snaps upstream of a REST Put Snap and prepare the following JSON file for the File Reader Snap: The Service URL for a REST snap has to be valid. If the Service URL contains any special characters, such as !, =, %21, $, and `^`, the Snap throws an exception error. You can escape the special characters (using expression language) using one of the following methods: Use the global function encodeURIComponent on any variables that might contain special characters so that they are encoded properly. For example, `'http://coresnapsqa-v4.s3.us-east-2.amazonaws.com/S3Account/'+encodeURIComponent(_fileName)` If you are aware of the code, use the code directly in the Service URL field. For example, http://coresnapsqa-v4.s3.us-east-2.amazonaws.com/S3Account/Special_char_owner_%213%2912.json; where <%213%2912> is the code. We recommend you to use the former (encodeURIComponent) method to escape the special characters.
HTTP Entity Default Value: $ (the HTTP entity data is at the root of the input Map data) Example: $.entity (if the HTTP entity data is the value of the "entity" key at the root of the input Map data)	String/Expression	Enter the JSON path to the HTTP entity data in the input Map data, or leave this field empty if there is no entity data to send to the service URL.
Batch size Default Value: N/A Example:2	String	Specify the batch size of the request. The incoming documents will be accumulated in a list up to the defined batch size before it is submitted to the endpoint. You must only set this if your REST endpoint expects a list.
Show all headers Default Value:Deselected	Checkbox	Select this checkbox to display the response header values as a list of objects in the output document. If any of these objects is a string in format "key1=value1; key2=value2; ...", it is parsed into a map data. The REST endpoint might return HTTP response with multiple headers with same header name. If you do not select this checkbox, only one response header is shown in the output document.
Upload transfer request type Default Value:Chunked transfer encoding Example:Calculate content length	Dropdown list	Choose the type of encoding that you want to use to safely transfer the entity to the user. The available options are: Chunked transfer encoding: On selecting this option, the Snap adds the header "`Transfer-Encoding:chunked`" to the PUT request, and uploads the given file in chunked transfer encoding format. Calculate content length: On selecting this option, the file size is calculated and passed with header "`Content-Length"` in the PUT request. You can use Chunked transfer encoding if the size of the given file cannot be calculated.
Form Upload	Use this field set to configure the fields required to upload multiple files and text. Learn more about Multipart Upload. By default, the Snap Settings display the fields required to upload a file. Click the Add icon to add new rows for adding file or text. This field set contains the following fields: Multipart Type Multipart Key Multipart Value HTTP Entity Filename to be used Multipart Content-Type Multiple file upload settings work similarly across the REST Post, Patch, and Put Snaps. To see an example of these settings in action, see Uploading Multiple Documents Using the REST Post Snap
Multipart Type Default Value: FILE Example: TEXT	Dropdown list	Choose the type of multipart upload that you want to initiate. The available options are: FILE: Use this option to upload a file. TEXT: Use this option to upload text.
Multipart Key Default Value: N/A Example: file	String/Expression	Enter the key for the multi-part form-data needed to upload a file. HTTP POST uses multi-part entity to achieve the file upload. The form-data of its multi-part entity contains key-value pairs. Upload-file key is dependent on the service endpoint. Multipart Key can be anything and it depends on the service endpoint. This property is expression-enabled. For more information on the expression language, see Understanding Expressions in SnapLogic and Using Expressions. For information on Pipeline Parameters, see Pipeline Properties.
Multipart Value Default Value: N/A Example: FILE: persons.csv TEXT: “sldb://file.txt”, “sampletext”	String/Expression	Specify the the file or text to be uploaded. If Multipart Type is FILE, the following are applicable: The file protocols supported for file values are 'sldb:///' and 'file:///'. If the file path is a relative path, it is considered as an SLDB file. If this field is not empty, HTTP Entity and Batch size fields are ignored and the Multipart Key field is required. If the value is an expression, the input document is used to evaluate the expression. Each input document invokes one file upload. This field does not support wildcard or glob patterns. If Multipart Type is a TEXT, then The value should be expression enabled and enclosed in double quotes. For Text part upload using Form Upload, the Http Entity and Filename to be used are ignored.
Filename to be used Example: file.csv	String/Expression	Enter the filename to be used for the new file created by the Snap.
Multipart Content-Type DefaultValue: N/A Example: text/csv	String/Expression/Suggestion	Select the content type headers for the data in the body of the multipart HTTP request. The available options are: application/octet-stream text/plain application/json text/csv text/html image/jpeg If the Multipart Type is TEXT, it is generally not required to specify any value in this field. When you do not specify any value, the API uses the default value `text/plain; charset=UTF-8`. To specify other HTTP headers configure the headers in the HTTP header field set. If you configure both Multipart Content-Type and HTTP header fields, the value in the Multipart Content-type gets precedence.
Trust all certificates Default Value:Deselected Example: N/A	Checkbox	Select this checkbox to trust all certificates, such as self-signed certificates.
Follow redirects* Default value: Selected	Checkbox	Select this checkbox to follow HTTP redirects. When selected, if a redirect response (e.g. a 301 or 302 response code) is received, another request to the URL specified in the Location header will be automatically made. When not selected, another request will not be made and the 301/302 response will show up in the output view.
Query parameters	Use this field set to define query parameters. This is optional and can either be defined directly in the service URL, as separate parameters or both. An example for OAuth2 (LinkedIn enabled endpoint).
Query parameter Default Value: N/A Example: oauth2_access_token	String/Expression	Specify the name for the query parameter.
Query parameter value Default Value: N/A Example: $account.access_token	String	Specify the value that you want to assign to the parameter.
HTTP header	Use this fieldset to specify the HTTP header key-value pairs. This field set contains the Key and Value fields.
Key Default Value: N/A Example: Content-Type	String/Expression	Enter the key for HTTP header.
Value Default Value: N/A Example: SnapLogic	String/Expression	Enter the value for the key parameter.
Response entity type Default value: DEFAULT	Dropdown list	Choose the response entity type in the output document. The available options include: DEFAULT - If selected, the response entity is processed automatically. The Snaps attempts to convert the entity to a string or a byte array depending on the response headers. TEXT - If selected, the Snap produces an entity of string type. BINARY - If selected, the Snap produces an entity of byte array type. If TEXT or BINARY is selected, the Snap will not attempt to parse the entity content. If DEFAULT is selected, the Snap produces the expected result in most cases, but when failed to do so, users may set the Response entity type to TEXT or BINARY.
Cookie Policy Default Value: Ignore Cookies Example: RFC Strict	Dropdown list	Select a Cookie Policy from the following options: Browser Compatibility: This policy is compatible with different servers even if they are not completely standards-compliant. If you are facing issues while parsing cookies, you should try using this policy. Ignore Cookies: This cookie policy ignores all cookies. You should use this policy to prevent HTTP Client from accepting and sending cookies. RFC Strict: This policy uses the `set-cookie` header RFC Lax: The policy uses `set-cookie` and `set-cookie2` for parsing. When using a cookie policy, you must select Show All Headers checkbox to view the parsed cookies from the cookie policy specification.
Read timeout Default Value: 900 seconds	Integer	Specify the time in seconds to wait before aborting the request due to a failure to read from the target service. This option lets you specify a timeout value in seconds after which the request gets aborted. In some cases, the request does not return, such as during network issues. For those a timeout can be configured to allow failing fast. Every Snap instance can have its own timeout settings. The Snap will execute five retries within a couple of seconds back-off time before it fails.
Connection timeout Default Value: 30 Example: 10	Integer	Specify the time in seconds to wait before aborting the request due to a failure to establish a connection to the target service.
Maximum request attempts Default Value: 5 Example: 3	Integer	Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response.
Retry request interval Default Value:3 Example:10	Integer	Specify the interval (in seconds) between two successive requests. A retry happens only when the previous attempt failed.
Retry Policy Default Value:Connection errors Example: Connection and server errors	Dropdown list	Choose the retry policy for connection and error responses. The available options are: Connection errors: Occur when a client fails to establish a secure connection to the server. Connection and auth errors (401/403): Occurs when either the user authorization fails or access to the page/resource is forbidden. Connection and client errors (4xx): Occurs when the request for the resource contains bad syntax, or when the resource is not found (404). Connection and server errors (5xx): Occurs when the server is unable to complete a request. All errors: Applies to all of the above-listed errors.
Normalize URL	Checkbox	Select this checkbox to normalize the Service URL. This enables the Snap to convert double slashes (//) in the URL path to single slash (/). For example, https://example.com/path//to//file is converted to https://example.com/path/to/file. Deselecting this check box reverts the Snap to 4.19 Snaplex behavior, wherein the URL paths were not normalized by default. In the 4.20 Release, due to the HTTP client upgrade the URL paths were normalized by default. Hence, there was a change in behavior in handling the URL paths in 4.20 release when compared to 4.19. This change in behavior should not impact the existing Pipelines, because most of the websites map URL paths with double or single slashes to the same endpoint. For example, https://snaplogic.com/company/diversity and https://snaplogic.com//company//diversity direct to the same endpoint. Therefore, we recommend you to select the Normalize URL checkbox. However, an exception to this is when you use non-standard URLs that differentiate the URL paths containing double slashes from those with single slashes and map them to different endpoints, in which case you must deselect Normalize URL check box. For example, http://host/pages/foo.html and http://host/pages//foo.html point to different URIs, and servers assign different meanings to them. Default Value: Selected Example: Deselected
Snap Execution Default Value: Execute only Example: Validate & Execute	Dropdown list	Select one of the three modes in which the Snap executes. Available options are: Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime. Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data. Disabled: Disables the Snap and all Snaps that are downstream from it.

Troubleshooting

Error	Reason	Resolution
Failed to execute HTTP request	The Service URL must have a protocol, such as http://, https://.	Please check the Snap properties. Specifically, check your entry in the Service URL field.
Failed to execute HTTP request	<Service_URL>: Name or service not known. This basically means that the service URL you entered is not accessible.
Failure: Validation errors: property_map.settings.serviceUrl.value: Could not compile expression: <Service_URL>	The snap settings are not correct. Encountered extraneous input ':' at line 1:5; expecting={<EOF>, '\|\|', '&&', '^', '==', '!=', '>', '<', '>=', '<=', '+', '-', '', '/', '%', '?', 'instanceof', 'in', 'matches', '[', '(', '.', PropertyRef}. This means that you have turned expressions on () while entering string value into the Service URL* field.	Please fix the snap configuration and try the execution again. Please check expression syntax. Specifically, ensure that your service URL is a proper expression; or turn off the expression control (). For more information on the expression language, see Understanding Expressions in SnapLogic and Using Expressions.
HTTP entity: <string_in_HTTP entity field> is undefined. Perhaps you meant: <List of variables received from the upstream Snap>.	Either there is an error in the value in the HTTP entity field, or you have used string input while having expressions enabled.	Check the spelling of the variable. Also, check whether your HTTP entity entry requires expressions. Update Snap settings as appropriate.
REST API service endpoint returned error result: status code = 400	Reason phrase = BAD REQUEST, refer to the error_entity field in the error view document for more details. You typically see this message when: The value in the HTTP entity field is structured as an expression; but the expression toggle is off. The value in the (single- or multiple-file-upload) File Key fields is inaccurate or does not contain expressions even though the Expression toggle is enabled. The value in the (single- or multiple-file-upload) File Name fields contains special characters, such as (&, ^, and %).	Check the values of Snap properties. Specifically: Check whether your HTTP entity entry requires expressions. Update Snap settings as appropriate. Check the value in the (single- or multiple-file-upload) File Key fields. Check the value in the (single- or multiple-file-upload) Filename to be used fields.
File not found: <File URL>	File not found on <server URL> at <complete address of file to be uploaded>	Address the reported issue. Check the location of the file to be uploaded.
Single file upload: <Name of field>: <name of file> is undefined. Perhaps you meant: <options based on your input>	null	Check the spelling of the variable. Specifically, check whether the expressions toggle is turned on even though it is not required.
REST API service endpoint returned error result: status code = 409	CONFLICT, refer to the error_entity field in the error view document for more details. This happens when you already have the resource that you want to create in the target endpoint.	Check the values of Snap properties.
URL Parse Exception - 403	The Service URL path might be containing any of the following special characters: !, =, %, #, $, ^&()_¢äâêîôûñç¡¿ÉÙËÇ¨°¸ðø©¢¾A+²½µ®§÷¶þ	To escape the special characters, use the global function encodeURIComponent on any variables that might contain special characters so that they are encoded properly.
Too many Requests - 429	There are too many requests to REST endpoint.	Wait for the retry to succeed. Rest related Snaps extract the response header and automatically retry when they encounter status 429. By default, the retry interval (Retry-After) is specified in the HTTP response header. If no value is available for Retry-After, then the Snap’s Retry Interval value is used.

Examples

Adding Members to SnapLogic Groups

In this example, we add members to a SnapLogic group.

We design the Pipeline as shown below:

We configure the JSON Generator Snap to enter details associated with the member that you want to add to the target group.

We configure the REST Put Snap, enter the account details in the Account tab, and configure the Snap to send the REST request to the endpoint.

We enter the service URL associated with the group in which you want to add the member. For information on creating the service URL, see Update Member List.
We specify a header to the call, indicating that the "Content-Type" in the body of your REST call is "application/JSON".

We save and execute the Pipeline. Once the Pipeline completes executing, the REST Put Snaps displays details associated with the operation performed.

Download this Pipeline.

Downloads

Important steps to successfully reuse Pipelines

Download and import the pipeline into the SnapLogic application.
Configure Snap accounts as applicable.
Provide pipeline parameters as applicable.

	File	Modified
Labels No labels Preview View	File RESTPut_Example.slp	Aug 04, 2020 by Mohammed Iqbal

Snap Pack History

Click to view/expand

Release	Snap Pack Version	Date	Type	Updates
August 2024	main27765	21 Aug 2024	Stable	Upgraded the `org.json.json` library from v20090211 to v20240303, which is fully backward compatible.
May 2024	437patches26522	12 Jun 2024	Latest	Enhanced the REST OAuth2 Account with Snaplex support for executing OAuth2 operations.
May 2024	main26341	08 May 2024	Stable	Updated and certified against the current SnapLogic Platform release.
February 2024	main25112	14 Feb 2024	Stable	Updated and certified against the current SnapLogic Platform release.
November 2023	main23721	08 Nov 2023	Stable	Updated and certified against the current SnapLogic Platform release.
August 2023	main22460	16 Aug 2023	Stable	Updated and certified against the current SnapLogic Platform release.
February 2023	main21015	10 May 2023	Stable	Upgraded with the latest SnapLogic Platform release.
February 2023	432patches20054	09 Mar 2023	Latest	For Snaps using AWS Signature V4 accounts, DNS canonical names are now supported for S3 buckets.
February 2023	main19844	09 Feb 2023	Stable	Upgraded with the latest SnapLogic Platform release.
November 2022	main18944	10 Nov 2022	Stable	Upgraded with the latest SnapLogic Platform release.
September 2022	430patches17851	16 Sep 2022	Latest	The REST Post Snap now works without displaying any errors when the Show all headers checkbox is selected and the Content-type is text/xml or application/xml.
August 2022	430patches17684	30 Aug 2022	Latest	The REST AWS Sig v4 Account is now enhanced with the AWS Region and Service Name fields that enable the Snap to support Virtual Private Cloud (VPC) endpoint.
August 2022	main17386	11 Aug 2022	Stable	You can set cookie policy specifications using the Cookie Policy dropdown list in REST Snaps . Support for auto-retries where the REST Snaps automatically retry when they encounter 429 HTTP status code - `Too Many Requests` error. The REST AWS Sig v4 Account supports: Passing AWS Security Token Service (STS) temporary credentials in the Security Token field. Expression values for Access-key ID and Secret Key fields. Improved the performance of REST Snaps when the Snaps encounter Unauthorized (401) or Forbidden (403) errors even when the user credentials are available in the organization and the account type is OAuth2.
4.29 Patch	429patches17084	19 Jul 2022	Latest	Enhanced the following REST Snaps with Cookie Policy dropdown list to set the cookie policy specifications. This field is case-insensitive: REST Delete REST Get REST Patch REST Post REST Put Learn more Cookie Policy: The Cookie Policy to select from the following options: BROWSER COMPATIBILITY: This policy is compatible with different servers even if they are not completely standards-compliant. If you are facing issues while parsing cookies, you should try using this policy. IGNORE COOKIES: This cookie policy ignores all cookies. You should use this policy to prevent HTTP Client from accepting and sending cookies. RFC STRICT: All servers that handle version 1 cookies should use this policy. RFC LAX: The original cookie specification which formed the basis for RFC2109. Added a new field Security Token in the REST AWS Sig v4 Account to support AWS Security Token Service (STS) for using temporary credentials. Enhanced the REST AWS Sig v4 Account to support expression values for Access-key ID and Secret Key fields.
4.29 Patch	429patches16076	20 May 2022	Latest	Enhanced the REST Snaps with support for auto-retry where the Snap retries automatically when the Snap encounters 429 HTTP status code - Too many requests error. Improved the performance of REST Snaps when the Snaps encountered errors due to Unauthorized (401) or Forbidden (403) statuses though the user credentials are available in the organization and the account type is OAuth2.
4.29	main15993	14 May 2022	Stable	Added the REST In-memory OAuth2 Account type with Client Credentials Grant Type that supports and stores the access token in memory for reuse until it expires. When the Snap encounters `401` or `403` errors, this account generates a new token after refreshing the cache.
4.28 Patch	428patches15172	28 Mar 2022	Latest	Fixed an issue that caused REST SSL accounts to fail when the username in the REST SSL Account was null and the Enhanced Encryption level was low, medium, or high.
4.28	main14627	12 Feb 2022	Stable	Enhanced the REST Post, REST Put, and REST Patch Snaps with the Multipart Type list to support multipart (files and text) upload. Renamed the following fields: Upload File(s) field set to Form Upload Upload-file key to Multipart Key Upload file to Multipart Value
4.27 Patch	427patches12750	01 Dec 2021	Latest	Enhanced the REST Put Snap with the Upload Transfer Request Type field to support encoding of chunked transfer and calculating content length.
4.27	main12989	15 Nov 2021	Stable and Latest	Fixed an issue in the REST OAuth2 account that caused a new feature, OAuth Password Grant Type to be excluded from the GA version. The latest deployed build includes this feature.
4.27	main12833	13 Nov 2021	Stable	Enhanced REST OAuth2 accounts with a new option password for Grant Type to obtain an access token through user credentials. On selecting password, the Snap populates the Username and Password fields to enter the credentials.
4.26	426patches12749	08 Nov 2021	Latest	Fixed an issue with the REST Post Snap, where the Snap delayed the fetching of documents, when the batch size is greater than or equal to one.
4.26	426patches11746	01 Oct 2021	Latest	Enhanced the REST Post Snap to display all cookies (`securedauth` cookies and `httponly` cookies) from the CookieStore along with headers when you select the Show all headers checkbox.
4.26	main11181	14 Aug 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.25 Patch	425patches10419	21 Jul 2021	Latest	Fixed a memory leak issue in the REST Snap Pack
4.25 Patch	425patches9929	13 Jul 2021	Latest	Enhanced the REST Snap Pack to support Proxy Authentication.
4.25 Patch	425patches9684	20 May 2021	Latest	Fixed the REST Post Snap that fails to correctly set the Content-Length header when working with multi-file uploads. Added Send Client Data as Basic Auth Header check box to the OAuth2 and OAuth2 SSL accounts. This check box enables you to include and pass the client credentials information in the header when connecting to the OAuth endpoint. Added a new account type REST AWS Sig V4 Account that adds the ability to call any AWS API.
4.25	main9554	08 May 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.24	main8556	13 Feb 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.23	main7430	14 Nov 2020	Stable	Improved the handling of expired access tokens in REST Snaps that use OAuth2 accounts (REST OAuth2 Account and REST OAuth2 SSL Account). The Snaps can refresh expired access tokens on-demand, through a request to the platform. The Snap reloads the account with the updated/fresh access token before attempting the next retry.
4.22 Patch	422patches7103	19 Oct 2020	Stable	Enhances the Snaps in REST Snap Pack by separating the retry logic for OAuth account from that of the Snap.
4.22	main6403	12 Sep 2020	Stable	Added a new account type, REST OAuth2 SSL, which enables support for the OAuth2 SSL authentication for REST Snaps with endpoints that require client certificates. [Docs Update] Applied the enhanced doc template to the Snap Pack's documentation. Improves usability by enhancing Snap field descriptions, functional examples, and use cases.
4.21 Patch	rest8858	-	Latest	Fixed the REST Get and REST Post Snaps that does not parse Content-Encoding and Content-Type headers for gzipped responses.
4.21	snapsmrc542	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.20 Patch	rest8798	-	Latest	Fixed the REST POST Snap that fails when a single file is uploaded in multi-part form using the Single file upload Snap settings.
4.20	snapsmrc535	-	Stable	The new Multipart related option in the Upload body type property in the REST Post Snap enables you to post files to the Google Drive API and retain the original names. The REST Account now has a new Grant Type option called Client Credentials. This enables the Snap to obtain an access token to the client ID and client secret through the token endpoint URL.
4.19 Patch	rest8374	-	Latest	Added a drop-down property Retry Policy to the REST Snaps to provide users with different retry options for connection and 4xx and 5xx error responses. Fixed the REST GET Snap that limits the output to five documents, even when more output documents are expected. Critical fix If your current or new Pipelines with REST Snaps use the retry functionality, then we recommend you to use this latest patch version as subsequent GA releases may result in Pipeline executions failing. Else, you can continue using your existing Snap Pack version (stable distribution – snapsmrc528).
4.19	snapsmrc528	-	Stable	Fixed a regression issue wherein REST Snaps are unable to handle empty XML responses when Show All Headers is enabled.
4.18	snapsmrc523	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.15 Patch	rest6310	-	Latest	Fixed an issue with the NLTM Rest account connection hanging infinitely.
4.15	snapsmrc500	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.14 Patch	rest6159	-	Latest	Fixed an issue wherein the REST GET and POST Snaps were infinitely trying to connect to endpoint even after pipeline execution abortion.
4.14 Patch	rest5782	-	Latest	Fixed an issue wherein the REST POST Snap was not accepting any blank values from upstream Mapper Snap.
4.14 Patch	rest5719	-	Latest	Fixed an issue where the Ultra task was not producing a valid response while acknowledging documents.
4.14	snapsmrc490	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.13 Patch	NA	-	Latest	REST POST Snap: New properties: Multipart Content-Type, and Filename to be used added.
4.13	snapsmrc486	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.12 Patch	rest4917	-	Latest	Fixed an encoding issue with the REST Get Snap so that it uses the same encoding format (UTF-8) by default on all machines instead of using a different encoding format based on the machine's Operating System.
4.12 Patch	rest4816	-	Latest	Fixed an issue that caused the REST OAuth accounts to fail when running in orgs with Enhanced encryption in Medium or higher level.
4.12 Patch	rest4781	-	Latest	Enhanced REST Post Snap to prevent it from encoding file names.
4.12	snapsmrc480	-	Stable	Added Upload body type property to the REST Post Snap for processing the specified content type.
4.11 Patch	rest4333	-	Latest	Added support for the Binary File Uploads with the REST POST Snap.
4.11	snapsmrc465	-	Stable	Updated support of NTLM Account Authentication to the REST Snap Pack.
4.10 Patch	rest4070	-	Latest	Resolved an issue with the REST GET Snap that often fails to exit properly. This should reduce or eliminate that problem.
4.10	snapsmrc414	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.9 Patch	rest3177	-	Latest	Addressed an issue with REST Get displaying the authorization header in plain text
4.9 Patch	rest3126	-	Latest	Added Connection timeout property to specify the number of seconds to wait before terminating a connection. The Timeout property has been renamed to Read timeout.
4.9.0	snapsmrc405	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.8.0	snapsmrc398	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.7.0 Patch	rest2555	-	Latest	Addressed an issue in the REST Post Snap with the REST API not returning a full cookie response. Added Show all headers setting to the show full cookie response for the Post, Put, Patch and Delete Snaps.
4.7.0 Patch	rest2336	-	Latest	Resolved an issue with REST Get not handling multiple response cookies.
4.7.0 Patch	rest2260	-	Latest	Added a new "Follow redirects" setting to toggle whether redirects should be followed (default behavior is to follow redirects)
4.7.0	snapsmrc382	-	Stable	Updated Snaps in the REST Snap Pack with Response entity type field(The DEFAULT option under this property allows the backward compatibility. The addition of the property will not affect the existing production pipelines and allows them to run as before). Updated Snaps in the REST Snap Pack with Maximum request attempts and Retry request interval Upload fields. Updated the RESTPost Snap with Upload transfer request type field.
4.6.0 Patch	rest1992	-	Latest	Resolved an issue where Rest Snaps failed to process the received response that is encoded in charsets such as Windows-1252. This fix will process the response purely based on the charset provided in the Content-Type header.
4.6.0	snapsmrc362	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.5.1	rest1566	-	Latest	A new property was added to the REST Get Snap to specify the iteration interval for pagination. All Snaps now have at most one input and one output view.
4.5.0	snapsmrc344	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.4.1	NA	-	Latest	Resolved an issue with REST SSL Accounts with Username not send the Authorization header with the HTTP request.
4.4.0	NA	-	Stable	REST Get now supports using parameters from an input document in the Next URL Setting.
4.3.1	NA	-	Latest	Addressed a defect where REST GET Snap fails saying 'Scheme "http" not registered'
Fall Release 2015 (4.3.0)	NA	-	Stable	Two-way SSL support was added to the REST account. REST Get Now has support for iterating over additional result pages. Header variables are now being updated for each input REST Post Improved error handling messages. Resolved an issue with the Snap failing with "Failed to execute HTTP request" error.
September 5, 2015 (4.2.2)	NA	-	Latest	Maximum retries and Retry interval support added. Resolved an issue with using a REST Dynamic OAuth2 account with Facebook Graph API. REST Account: REST SSL account added.
June 27, 2015 (2015.22)	NA	-	Latest	REST Get now allows you to have no output views. Previously, there was exactly one output view.
June 6, 2015 (2015.20)	NA	-	Latest	Rest Post Snap now supports posting a file.
May 2, 2015	NA	-	Stable	REST: Output views made optional
January 2015	NA	-	Stable	Optional Raw data property added to all REST Snaps. If selected, the HTTP response content is written to the output view as is. If not selected, it is parsed according to the content type specified in the response header.
October 18, 2014	NA	-	Stable	NEW! REST Patch Snap introduced in this release. Addressed an issue where REST GET (and perhaps REST Snaps) error view does not include response body.
Fall 2014	NA	-	Stable	REST Get: support added for gzip format.
June 30, 2014	NA	-	Stable	Addressed an issue with RestRequestExecutor class writing data into error views even on successful requests status code 201, 204.
May 2014	NA	-	Stable	REST Get, REST Post all updated to support input parameters in HTTP headers
July 2013	NA	-	Stable	NEW! REST Delete Snap introduced in this release. NEW! REST Get Snap introduced in this release. NEW! REST Post Snap introduced in this release. NEW! REST Put Snap introduced in this release.

See Also

SnapLogic Community: Passing account credentials to an Authorization Endpoint via the JSON body or as an Expression