49 lines
3.0 KiB
JSON
49 lines
3.0 KiB
JSON
{
|
|
"type": "API Response Field Reference",
|
|
"definition": {
|
|
"text": "This node allow users to reference an API Data Field from a Record Property. In other words it allows to link each piece of data the user wants to be saved locally to the field at the API Map that will hold the data at runtime.",
|
|
"updated": 1621022976968
|
|
},
|
|
"paragraphs": [
|
|
{
|
|
"style": "Text",
|
|
"text": "Once created, you need to reference an API Data Field.",
|
|
"updated": 1621023087914
|
|
},
|
|
{
|
|
"style": "Important",
|
|
"text": "All references originating at the same Record Definition must be to API Data Field s living at the same API Endpoint."
|
|
},
|
|
{
|
|
"style": "Title",
|
|
"text": "Record Property Configuration"
|
|
},
|
|
{
|
|
"style": "Subtitle",
|
|
"text": "Properties"
|
|
},
|
|
{
|
|
"style": "Success",
|
|
"text": "nodePath is a property that is required when the API Response Field referenced is not under the Data Root object within the response structure.",
|
|
"updated": 1621969132831
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "The response from the API Server might include some header type of data and the actual data requested. Since the response is a JSON object, then the actual data might be located somewhere within the structure of that object. The API Response Schema node has a property nodePath that allows users to declare the path to the actual data requested, so as to jump the header-like information. We call the API Response Field where the data is held, the Data Root. "
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "In order to extract individual values for each Record Property, the API Data Fetcher Bot needs to dynamically discover the nodePath for each Record Property at the response data structure and can do it as long as the API Response Field referenced is under the Data Root. To auto discover the nodePath it uses the API Response Schema nodePath to locate the Data Root, and then it follows the reference from the API Response Field Reference node to the API Response Field and climbs upwards until it reach the API Response Schema. While climbing upwards it discovers the nodePath that it needs to grab the value from the response data structure. That is how it works.",
|
|
"updated": 1622372741883
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "When the referenced API Response Field is outside the scope of the Data Root, the process is not able to auto discover this path and need users to manually define the nodePath (from the API Response Schema to the API Response Field that holds the value) and set it in this property. That happens for instance when the API Response Field is part of the header of the API Server response.",
|
|
"updated": 1621972505639
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": ""
|
|
}
|
|
]
|
|
} |