FAQ

Q1: How often should partners update data on their server?

A1: The frequency of data updates should be tailored to the specific needs and characteristics of each asset. Factors to consider include data volatility, the criticality of having the most up-to-date information, and the nature of the application using the data. Partners should aim for a balance between providing timely updates and minimizing unnecessary load on their servers.

Q2: What should I do if the data provided by an external API does not meet the required format?

A2: If the data from an external API does not meet the required format (e.g., price in numeric 18 decimals format, timestamp in UNIX seconds), you may need to preprocess the data before feeding it into the Entangle UDF system. This could involve converting data types, rounding floating-point numbers, or formatting timestamps.

Q3: Can Entangle UDF support custom modifiers for data parsing?

A3: Currently, the data parsing pipelines use GJSON syntax, which supports basic JSON parsing and querying. If you require custom modifiers for more complex parsing, please contact the Entangle team with your requirements, as there is potential for future support for custom modifiers.

Q4: How do I handle optional fields like timestamp and volume in the server response?

A4: If the timestamp or volume is not provided in the server response:

• Timestamp: The system will assign the system time to the new update.

• Volume: If volume is not provided, VWAP (Volume Weighted Average Price) will be disabled. Ensure your configuration accounts for these defaults if the data source does not include these fields.

Q5: Can I use public data providers for integration?

A5: Yes, you can use public data providers for integration. You will need to provide the URL specification for the public data provider's API. From there, you can create a URL template and pipelines for parsing the necessary data.