Informatica Cloud Spring REST API Connector Guide

Transcription

1 Informatica Cloud Spring 2017 REST API Connector Guide

2 Informatica Cloud REST API Connector Guide Spring 2017 December 2017 Copyright Informatica LLC 2016, 2018 This software and documentation are provided only under a separate license agreement containing restrictions on use and disclosure. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica LLC. U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation is subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR , Commercial Computer Software License. Informatica, the Informatica logo, Informatica Cloud, and PowerCenter are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at Other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties. Required third party notices are included with the product. See patents at DISCLAIMER: Informatica LLC provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica LLC does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. The information in this documentation is subject to change without notice. If you find any problems in this documentation, report them to us at infa_documentation@informatica.com. Informatica products are warranted according to the terms and conditions of the agreements under which they are provided. INFORMATICA PROVIDES THE INFORMATION IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT. Publication Date:

3 Table of Contents Preface... 5 Informatica Resources Informatica Documentation Informatica Cloud Web Site Informatica Cloud Communities Informatica Cloud Marketplace Informatica Cloud Connector Documentation Informatica Knowledge Base Informatica Cloud Trust Site Informatica Global Customer Support Chapter 1: Introduction to REST API Connector... 7 REST API Connector Overview Chapter 2: REST API Connections... 8 REST API Connections Overview REST API Connection Properties General Properties URL Properties Form Properties Header Properties Authentication Properties Creating Configuration Files Using Configuration Files Order of Precedence for Request details Chapter 3: REST API Operations REST API Operations Overview Making a GET Request Create a REST API Connection Create a Data Synchronization Task Making a POST Request Create a Connection Create a Data Synchronization Task Chapter 4: Custom Authentication for REST API Custom Authentication for REST API Overview Implementing the Java Template Deploying the CusthomAuth JAR File Table of Contents 3

4 Appendix A: Proxy Configuration Configuring Proxy Settings Index Table of Contents

5 Preface The Informatica Cloud REST API Connector Guide contains information about how to set up and use REST API Connector. The guide explains how organization administrators and business users can use REST API Connector to read data from and write data to a REST API. Informatica Resources Informatica Documentation To get the latest documentation for your product, browse the Informatica Knowledge Base at If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at infa_documentation@informatica.com. Informatica Cloud Web Site You can access the Informatica Cloud web site at This site contains information about Informatica Cloud editions and applications as well as information about other Informatica Cloud integration services. Informatica Cloud Communities Use the Informatica Cloud Community to discuss and resolve technical issues in Informatica Cloud. You can also find technical tips, documentation updates, and answers to frequently asked questions. Access the Informatica Cloud Community at: To find resources on using Cloud Application Integration (the Informatica Cloud Real Time service), access the community at: Developers can learn more and share tips at the Cloud Developer community: 5

6 Informatica Cloud Marketplace Visit the Informatica Marketplace to try and buy Informatica Cloud Connectors, Informatica Cloud integration templates, and Data Quality mapplets: Informatica Cloud Connector Documentation You can access documentation for Informatica Cloud Connectors at the Informatica Cloud Community: You can also download individual connector guides: Informatica Knowledge Base Use the Informatica Knowledge Base to search Informatica Network for product resources such as documentation, how-to articles, best practices, and PAMs. To access the Knowledge Base, visit If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team at Informatica Cloud Trust Site You can access the Informatica Cloud trust site at This site provides real time information about Informatica Cloud system availability, current and historical data about system performance, and details about Informatica Cloud security policies. Informatica Global Customer Support You can contact a Customer Support Center by telephone or online. For online support, click Submit Support Request in the Informatica Cloud application. You can also use Online Support to log a case. Online Support requires a login. You can request a login at The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at 6 Preface

7 C h a p t e r 1 Introduction to REST API Connector This chapter includes the following topic: REST API Connector Overview, 7 REST API Connector Overview Use REST API Connector to integrate data with REST-based web service applications that are either internal to an organization or external applications. You can use REST APIs as sources and targets in Data Synchronization tasks, mappings, and Mapping Configuration tasks. The REST API Connector supports web services that conform to REST methods. The REST Connector supports URL encoding in the request URL parameter. REST API Connector supports following request types: GET POST PUT DELETE REST API Connector supports following authentication types: NO AUTH BASIC AUTH DIGEST AUTH OAUTH CUSTOM AUTH REST API Connector supports following media types: application/xml application/json 7

8 C h a p t e r 2 REST API Connections This chapter includes the following topics: REST API Connections Overview, 8 REST API Connection Properties, 8 Creating Configuration Files, 11 Using Configuration Files, 14 Order of Precedence for Request details, 15 REST API Connections Overview Create a REST API connection to make calls to the REST APIs. While creating a connection, you specify the Base URL of the REST API to which you want to make calls. Use REST API connector as a source or a target when you create mappings, Mapping Configuration tasks, and Data Synchronization tasks. You create a REST API connection on the Connections page. REST API Connection Properties When you set up a REST API connection, you must configure the connection properties. Consider the following categories for the REST API connection properties: General properties URL properties Form properties Header properties Authentication properties 8

9 General Properties The following table describes the REST API connection general properties: Connection Property Connection Name Type Runtime Environment Sample Response XML or JSON File Path Response Folder Path Name of the REST API connection. Enter a unique name for the connection. of the connection. The description cannot exceed 765 characters. Type of connection. Select REST (Informatica Cloud Labs) from the list The name of the runtime environment where you want to run the tasks. Do not use the Hosted Agent. Provide the path of the xml or JSON response file. - If you provide the path of the response file, the Secure Agent does not make a call to the REST API during the design phase. - If you do not provide the path of the response file, the Secure Agent makes a call to the REST API during the design phase. Provide the path on Secure Agent machine where you want to generate the response file. URL Properties The following table describes the REST API connection URL properties: Connection Property Base URL Is BaseURL Dynamic Url Request Parameters Media Type Endpoint URL of REST API to which you want to make calls. Do not specify the query parameters with the Base URL. Select if you want to make multiple calls and the Base URL for each call is different. If the Base URL is dynamic, the Secure Agent uses the base URLs specified in the Parameter Configuration file. In the Parameter Configuration file, you must add Dynamic_BaseUrl column and provide the URL for each request as the values. For more details about the Configuration files, see Creating Configuration Files on page 11 Specify the URL request parameters separated by semicolon (;) based on Endpoint URL you provide in the Base URL parameter. For example: An invoice report API might require the following parameters: apiversion=5.3;passkey=tro5yhjgtyfdsay9jbjojc;sort=rating:desc;limit=7;include=products; The parameter and the value are separated by an equal sign (=). Select the required media type from the list. - application/xml - application/json - application/x-www-form-urlencoded - text/xml - text/plain REST API Connection Properties 9

10 Connection Property Request Type Url Input Parameters Config File Name Select the required Request Type from the list. - GET - POST - PUT - DELETE Optional. Specify the path and name of the configuration file. When the file is created for the first time, it contains the values that are provided in the Url Request Parameters field. Later, you can add different values for different records in the configuration file. Note: The Url request parameter must not contain semicolon (;) and the parameter value must not contain the equal sign (=). Use the Create the config csv file property to create the configuration files if you want to pass multiple values for parameters defined in the URL Input Parameters, Form Input Parameter, or Header Input Parameter fields. For more details, see Creating Configuration Files on page 11. In addition to provide the Url request parameters and the Url input parameters configuration file in the connection properties, you must set the parameters when you configure the source or the target. Set the parameters in the Filter page if the REST connection is a source or in the Mapping page if the REST connection is a target. Form Properties The following table describes the REST API connection Form properties: Connection Property Form Request Parameters Form Input Parameters Config File Name Specify the Form request parameters separated by semicolon (;) based on Endpoint URL you provide in the Base URL parameter. For example: A login API requires the user name and password parameters. username=peter@foobar.com;password=foobar1 The parameter and the value are separated by an equal sign (=). Optional. Specify the path and name of the configuration file. When the file is created for the first time, it contains the values that are provided in the Form Request Parameters field. Later, you can add different values for different records in the configuration file. Note: The Form request parameter must not contain semicolon (;) and the parameter value must not contain the equal sign (=). In addition to provide the Form request parameters and the Form input parameters configuration file in the connection properties, you must set the parameters when you configure the source or the target. Set the parameters in the Filter page if the REST connection is a source or in the Mapping page if the REST connection is a target. 10 Chapter 2: REST API Connections

11 Header Properties The following table describes the REST API connection header properties: Connection Property Header Request Parameters Header Input Parameters Config File Name Specify the header request parameters separated by semicolon (;) based on Endpoint URL you provide in the Base URL parameter. For example: An invoice report API might require the following parameters: X-SAMPLE-API-KEY=24d21ab51e9d40b7cd6f765a7fb42aaebe60e2ba8;ACCEPT=application/xml The parameter and the value are separated by an equal sign (=). Optional. Specify the path and name of the configuration file. When the file is created for the first time, it contains the values that are provided in the Header Request Parameters field. Later, you can add different values for different records in the configuration file. Note: The header request parameter must not contain semicolon (;) and the parameter value must not contain the equal sign (=). In addition to provide the Header request parameters and the Header input parameters configuration file in the connection properties, you must set the parameters when you configure the source or the target. Set the parameters in the Filter page if the REST connection is a source or in the Mapping page if the REST connection is a target. Authentication Properties Configure the authentication type and the required authentication properties for secure communication between the Secure Agent and REST API endpoint. The following is the list of authentication types and the required authentication properties: No AUTH. BASIC AUTH. Provide Auth UserId and Auth Password. DIGEST AUTH. Provide Auth UserId and Auth Password. OAUTH. Provide OAuth Consumer Key, OAuth Consumer Secret, OAuth Token, and OAuth Token Secret. CUSTOM AUTH. Provide Additional Custom OAuth Parameters. For more details about the Custom AUTH, see Custom Authentication for REST API Overview on page 26. Creating Configuration Files Use configuration files when you want to pass different values for the parameters defined in the URL input parameter, form input parameter, or header input parameter to the dynamic base URL. With the URL Request Parameters, Form Request Parameters, or Header Request Parameters fields, you can pass a single value to the parameters. With the configuration files, you can pass different values for different records. You can create sample configuration files with a valid syntax and then populate different values for different records. Creating Configuration Files 11

12 To create a sample configuration file, you must first mention at least one parameter-value pair in the URL Request Parameters, Form Request Parameters, or Header Request Parameters fields as required. Perform the following steps to create a sample URL input parameter configuration file: 1. Click Configure > Connections, and then click New. 2. On the New Connection page, configure the following connection details: Connection Detail Connection Name Type Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _. + - Connection names are not case sensitive. of the connection. Maximum length is 255 characters. Select ReST (Informatica Cloud OEM Labs) 3. Configure the configuration files-specific properties. For example, to create a sample URL input parameter configuration file, enter the runtime environment to be used with the connection, the Base URL of the REST API to which you want to make calls, the parameter-value pair in the URL Request Parameters field, path and name of the property file, and Yes in the Create the config csv file field. The following image shows the property fields for the URL input parameter configuration file: 12 Chapter 2: REST API Connections

13 4. Click Test. If the test for the connection is successful, the sample configuration file, foobar.csv, is created at the specified location, E:\sample\Files\ReST\Config. Similarly, you can create the sample form and header input parameter configuration files. Creating Configuration Files 13

14 Using Configuration Files After you have created and added different values to the parameter configuration files, you can configure the same in the connection. For example, the following image shows the connection configuration where the URL and header input parameter configuration files have been used: Note: Select No in the Create the config csv file field when you want to use a parameter configuration file in the connection. 14 Chapter 2: REST API Connections

15 Order of Precedence for Request details You can configure URL parameters, Header, and Form Input request details in multiple places. The following places where you can specify the request details are: Connection property Filters and Field Mappings Input parameter configuration file You must specify request details in Connection property to fetch the metadata. If you specify request details in Filters or Field Mappings, and Input Parameter Configuration file during runtime, details specified in the Input Parameter Configuration file takes precedence. Order of Precedence for Request details 15

16 C h a p t e r 3 REST API Operations This chapter includes the following topics: REST API Operations Overview, 16 Making a GET Request, 16 Making a POST Request, 21 REST API Operations Overview You can perform GET, POST, PUT, and DELETE operations using REST API Connector. Making a GET Request You are a weather analyst. Using Informatica Cloud, you want to use a RESTful service to read the weather data of any city for analysis. In this example, you pass the required city names as data filters, receive the JSON message format output, and write the output to a.csv file. Perform the following steps: 1. Create a REST API Connection to use as a source. a. Create a URL input parameters config file. b. Use the URL input parameters config file in the connection. 2. Create a Data Synchronization task. a. Configure source to access REST API endpoint. b. Configure target to write data to a flat file. c. Configure data filters. d. Map the fields. e. Save and run the Data Synchronization task. Create a REST API Connection 1. Click Configure > Connections. 16

17 2. Click New to create a connection. 3. Specify the following details: Connection Property Connection Name Type Runtime Environment Base URL Is Base Url Dynamic Url Request Parameters Form Request Parameters Header Request Parameters Media Type Request Type Authentication Type Auth UserId Auth Password OAuth Consumer Key OAuth Consumer Secret OAuth Token OAuth Token Secret Additional Custom OAuth Parameters Config File or Private Key File Name Sample Response XML or JSON File Path Response Folder Path Enter a unique name for the connection. For example: OpenWeather_REST Provide a relevant description for the connection. Select ReST (Informatica Cloud Labs) Select the appropriate Secure Agent. Checked q=bangalore;appid=70ab007d4fe120b85d11d5432cbe7609 N/A N/A Select application/json Select GET NO_AUTH N/A N/A N/A N/A N/A N/A N/A N/A N/A Specify a path on the Secure Agent machine where you want to generate the response file. For example: C:\Informatica\Cloud\FlatFile_Connections\Weather Making a GET Request 17

18 Connection Property Url Input Parameters Config File Name Form Input Parameters Config File Name Header Input Parameters Config File Name Create the config csv file Specify the path and name of the config file. For example: C:\Informatica\Cloud\FlatFile_Connections\Weather\config.csv When the file is created for the first time, it contains the values that are provided in the Url Request Parameters field. N/A N/A Select Yes 4. Click Test to create the Url Input Parameters config file. 5. Select No in the Create the config csv file parameter as shown in the following image: 18 Chapter 3: REST API Operations

19 6. Click OK to create the connection. Open the config.csv file. The following image shows the sample config file: Add the additional parameter values with a valid syntax. The following image shows the sample config file after adding additional parameter values: Making a GET Request 19

20 Create a Data Synchronization Task 1. Click Task Wizards > Data Synchronization, and then click New. 2. Select Synchronization Task and click Create. 3. In the New Data Synchronization Task Details page, configure the following fields: Field Task Name Task Operation Name of the Data Synchronization task. For example: REST_GetWeather_By_City of the Data Synchronization task. Maximum length is 255 characters. Select Insert. 4. Click Next. 5. On the Source page, configure the following fields: Field Connection Source Type Source Object Select the connection you created. For example: OpenWeather_REST Select Single. Select JsonRoot. 6. Click Next. 7. On the Target page, configure the following fields: Field Connection Target Object Select the flat file connection. Click Create Target. Change the default file name to WeatherByCity.csv and select all fields in the file. 8. Click Next. 9. On the Data Filters page, create a new filter and filter by _FLT_URL_Input_Parameters_Config_File_Path. Provide the path and name of the config file that contains different values for different records: The following image shows the data filter: 10. Click Next. 20 Chapter 3: REST API Operations

21 11. On the Field Mapping page, click Automatch. 12. Click Validate Mapping. 13. Save and run the Data Synchronization task. The following image shows the sample output: You can also create a mapping or Mapping Configuration task to make a GET request. 14. Configure advanced source properties. Advanced source properties appear on the Schedule page of the Data Synchronization Task wizard. The following table describes the advanced source properties that you can configure for a REST API source: Field Time delay in ms Retry Count Specifies the amount of time (milliseconds) to wait before the connector retries for a response. Specifies the number of tries to get the response from an endpoint based on the time delay. Note: If the connector is not able to get response based on the time delay in ms and retry count properties, it throws an exception. Making a POST Request You are an operation manager in a marketing services organization. At a regular interval, you need to tweet the marketing content for your multiple clients. Instead of accessing Twitter account for each client every time, you can use Informatica Cloud REST API Connector to call the Twitter Update API. To make a POST request to a REST API, you configure the payload required by the API when you create a task. The Twitter Update API does not require a payload. Therefore, in this example, you configure the text to be tweeted in Field Mapping without configuring a payload. This example does not parse the response of the POST request. Perform the following steps: 1. Create a REST API Connection to use as a target. 2. Create and run a Data Synchronization task. Create a Connection 1. Click Configure > Connections. 2. Click New to create a connection. The New Connection page appears. Making a POST Request 21

22 3. Specify the following details: Connection Property Connection Name Type Runtime Environment Base URL Url Request Parameters Media Type Request Type Authentication Type OAuth Consumer Key OAuth Consumer Secret OAuth Token OAuth Token Secret Create the config csv file Enter a unique name for the connection. Provide a relevant description for the connection. Select ReST from the list. Select the appropriate secure agent from the list. Enter status=testtweet Select application/json Select POST Select OAUTH Provide Oauth consumer key for your Twitter account. Provide Oauth consumer secret key for your Twitter account. Provide Oauth token for your Twitter account. Provide OAuth token secret for your Twitter account. Select No 22 Chapter 3: REST API Operations

23 The following image shows the sample values: 4. Click Ok to save the connection. Making a POST Request 23

24 Create a Data Synchronization Task For POST request, configure the REST API connection as target. Before you create a Data Synchronization task, create a flat file and save the text that you want to tweet. For example, TwitterStatus.txt. Create a flat file connection to use as a source. 1. Click Task Wizards > Data Synchronization, and then click New. 2. In the New Data Synchronization Task Details page, configure the following fields: Field Task Name Task Operation Name of the Data Synchronization task. For example: REST_TwitterUpdate of the Data Synchronization task. Maximum length is 255 characters. Select Insert. 3. Click Next. 4. On the Source page, configure the following fields: Field Connection Source Type Source Object Select the flat file connection. Select Single. Select TwitterStatus.txt. 5. Click Next. 6. On the Target page, configure the following fields: Field Connection Target Object Select the connection you created. For example: TwitterUpdate_REST Select update_json 7. Click Next. 8. On the Field Mapping page, map the TwitterStatus.txt source file to the URLPARAM_status field of the target object. If your POST call has a payload, define the payload in a flat file, and map the absolute path of the file to PAYLOAD_FileName in Field Mapping. The following image shows the field mapping for URLPARAM_status: field: 24 Chapter 3: REST API Operations

25 9. Click Validate Mapping. 10. Save and run the Data Synchronization task. Making a POST Request 25

26 C h a p t e r 4 Custom Authentication for REST API This chapter includes the following topics: Custom Authentication for REST API Overview, 26 Implementing the Java Template, 27 Deploying the CusthomAuth JAR File, 27 Custom Authentication for REST API Overview You can use multiple authentication types at the REST API endpoint and server, such as OAuth, Basic, Digest, and other custom authentication. To implement your own authentication logic, use the Custom Authentication function. You can also use the predefined java template to implement your authentication logic. The java template consists of a method, an Inner Class and an Enum. Method Method signature is: String GetCustomAuthParams(RequestInfo,Ilogger) RequestInfo A bean class that captures all the connection UI parameters. Inner Class Enum CustomParams is the inner class. The return value is always a vector of CustomParams Objects. Defines the types of parameter present in Custom Authentication. enumparamtype is the enum in the template. Note: If you want Informatica to create the custom authentication for you, contact Informatica Sales Team, Informatica Cloud API Response Team, or Informatica Customer Service. 26

27 Implementing the Java Template Implement the CustomAuth.java file to customize an authentication type. 1. Include new Form, Url, or Header parameters. 2. Implement the GetCustomAuthParams() method with the following method signature: String response GetCustomAuthParams(RequestInfo,Ilogger) 3. Define custom parameters for the inner class. 4. Set all the bean method values to use the custom parameter. Deploying the CusthomAuth JAR File Deploy the CustomAuth JAR file to customize an authentication type. 1. Create a copy of the CustomAuth.java file. 2. Name the file in the following format: CustomAuth_<UserCompanyName/EndpointName>.jar 3. Stop the Informatica Cloud Secure Agent service. 4. Copy the created jar file to the following locations: <Secure Agent installation directory>\apps\data_integration_server\ext\deploy_to_main \bin\rdtm-extra\rest\ Implementing the Java Template 27

28 A p p e n d i x A Proxy Configuration This appendix includes the following topic: Configuring Proxy Settings, 28 Configuring Proxy Settings You can enable or disable proxy for the REST API Connector irrespective of the Secure Agent proxy. Use the ProxySettings.ini in the Secure Agent directory to change the proxy settings. You need to set the value of setproxy attribute to either true or false to enable or disable the proxy. The following image shows an example of ProxySettings.ini file: If you use proxy support, perform the following steps: 1. Copy the ProxySettings.ini file from <Secure Agent installation directory>\downloads\<latest connector package>\package\plugins\rest\ to <Secure Agent installation directory>\apps \Data_Integration_Server\ext\deploy_to_main\bin\rdtm-extra\Rest\ Note: If the deploy_to_main\bin\rdtm-extra\rest\ directory does not already exist, create the directory. Note: The folder name is case sensitive on Linux. 2. Restart the Secure Agent. 28

29 I n d e x C Cloud Application Integration community URL 5 Cloud Developer community URL 5 configuration files creating 11 using 14 custom authentication overview 26 G GET request creating a connection 16 creating a data synchronization task 20 I Informatica Cloud Community URL 5 Informatica Cloud web site URL 5 Informatica Global Customer Support contact information 6 O overview custom authentication 26 overview (continued) REST API connection 8 REST API Connector 7 REST API operations 16 R REST API connection overview 8 properties 8 REST API connection properties authentication 11 Form 10 general 9 header 11 URL 9 REST API Connector authentication types 7 configuring proxy settings 28 media types 7 overview 7 request types 7 REST API operations overview 16 T trust site description 6 29