Difference between revisions of "Calling REST based Web services"

From Toolsverse Knowledge Base
Jump to: navigation, search
Line 3: Line 3:
 
Use JSON, XML or text to serialize datasets and objects.
 
Use JSON, XML or text to serialize datasets and objects.
  
You can include access tokens into the endpoint URLs. Example: https://host/rest/v1/data/?filter=Id&access_token={access_token}
+
You can include access tokens into the endpoint URLs. Example: https://host/rest/v1/data/?filter=123&access_token={access_token}
  
 
[https://www.toolsverse.com/products/etl-framework/examples/web_services/http_get.shtml Example of the GET request]
 
[https://www.toolsverse.com/products/etl-framework/examples/web_services/http_get.shtml Example of the GET request]
  
 
[https://www.toolsverse.com/products/etl-framework/examples/web_services/http_put.shtml Example of the PUT request]
 
[https://www.toolsverse.com/products/etl-framework/examples/web_services/http_put.shtml Example of the PUT request]

Revision as of 16:42, 22 December 2014

The ETL Framework natively supports REST based Web services. You don't need to do anything special, just make sure sources are linked to the GET endpoints and destinations - to the PUT endpoints.

Use JSON, XML or text to serialize datasets and objects.

You can include access tokens into the endpoint URLs. Example: https://host/rest/v1/data/?filter=123&access_token={access_token}

Example of the GET request

Example of the PUT request