Invoking atomic transformations

The contract of the atomic transformation invocation service is dynamic, based on the contract defined by source data and transformed data in the job.

The web service is based on JSON data. You need to provide the JSON data corresponding to the source record format of the job.

For instance, let's say a job defines the following JavaScript transformation with two source columns (POSTALCODE and COUNTRY):

The web service will therefore expect that each JSON record contains two values. The service accepts one or multiple records in it's payload. Use a HTTP POST with a body like this (3 records and 2 columns):

			{"rows":[
			  {"values":["2200","DK"]},
			  {"values":["2200",""]},
			  {"values":["DK2200","DK"]}
			]}
		

And the resulting response body will look like this:

			{
			  "rows":[
			    {"values":["DK2200"]},
			    {"values":["2200"]},
			    {"values":["DK2200"]}
			  ],
			  "columns":[
			    "Country postalcode"
			  ]
			}
		

Note that the 'Content-Type' header of the request is assumed to be 'application/json'.