Call URL allows a RESTful API call to be invoked. Darwinium attribute data can be injected into the request and extracted from the response. 
URL
Click the edit button next to URL to set the URL:
Method
Click the edit button next to Method to set the HTTP Method for the URL call. POST and GET are most common, however PUT, DELETE, PATCH and OPTIONS are all supported for a variety of use cases.
Request
The Request section is used to construct the HTTP request that is sent to the configured URL.
Header Content
The Header Content section can be used to add HTTP headers to the Request. The most important Header is the Content-Type header and the value must be set to the correct content type for the configured Request Body.
Click on the + button to add a HTTP header:
Header Name
This is where the name of the HTTP header is specified. Click on the edit button below Header Name to edit the Header Name:
Content
Click on the edit button below Content to set the value to be set for the configured HTTP header name.
String content can be used for static or Template Markup or a value can be injected directly from an Attribute.
Please refer to the Template Markup article for more information on Template Markup.
Multiple HTTP Headers can be added as required:
Body Content
The contents of the HTTP Request body are formed inside the Body Content section.
First select the appropriate Body Type
- body_rule - for JSON, XML or HTML
- multipart_body_rules - for multipart form data or URL encoded name/value pairs ONLY
Body Rule
The Body Rule type is used for injecting JSON, XML and HTML request bodies.
String Content
Simple request bodies can be constructed using the String Content option:
From a template file
For complex request bodies it is recommended to use a template file specified in Template Markup.
Template files work exactly the same as String Content, however they are stored in a separate template file to accomodate larger content.
Multipart Body Rules
Multipart Body rules are used for constructing either multipart form data or URL encoded name value pair request bodies.
Use the + button to add additional fields into the Request:
Field Name is the form field or name/value pair name and Content is the value assigned to the field.
Response
The Response section is used for extracting data from the HTTP response body into attributes for use in decisioning.
Header Mappings
Header mappings can be used to extract data from HTTP Headers into Attributes. Use the + button to add a new Header Mapping. Click on the edit button below Header Name to edit the name of the header and click on the edit button below operation to display the Injection and Extraction Menu to perform Data Mapping operations. Please refer to the Injection and Extraction Menu article for details of the options available.
Body Mappings
First select the appropriate Body Type
- body_rule - for JSON, XML or HTML
- multipart_body_rules - for multipart form data or URL encoded name/value pairs ONLY
Body Rule
Click on the edit button next to Body Rule to display the Injection and Extraction Menu to perform Data Mapping operations. Please refer to the Injection and Extraction Menu article for details of the options available.
Multipart Body Rules
Multipart Body Rules are used for processing Form Data and URL encoded name value pairs.
Use the + button to add a new field mapping. Click on the edit button below Field to set the name of the field being mapped. Next click on the edit button below operation to display the Injection and Extraction Menu to perform Data Mapping operations. Please refer to the Injection and Extraction Menu article for details of the options available.
