What this category of data looks like
In software development scenarios, revenue yield and market daily report data is generated by integrating with trading system APIs, custodian valuation files, and internal transaction logs. Full complete data is updated before 03:00 each day. Incremental market snapshots refresh every 15 minutes. The data uses a structured format, with each record corresponding to the daily market data of a single financial product. It includes fields including product_code, product_name, total_market_value, daily_trade_amount, daily_profit_amount, and trade_count. Units are as follows: product codes and names have no unit; market value and amount fields use yuan; trade count is measured in transactions.
What constraints do these characteristics impose on the sharing and embedding workflow
The requirement for structured fixed fields means sharing links must carry clear product scope and date parameters. Otherwise, target data cannot be rendered correctly. The fixed daily update rhythm means embedded pages must match the data refresh cycle to avoid displaying expired information. The high-frequency refresh requirement for incremental snapshots means shared embedded interfaces must support short-cycle cache configuration. This balances data timeliness and request load. The need for identity verification means sharing links must bind identity parameters from the business system. This adapts to exclusive data access needs for different clients.
How to Configure Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
share_link_default_params | {"date": "latest", "product_scope": "all"} | Adapts to the default display needs of daily reports, pointing to full product data for the most recent trading day |
iframe_allow_credentials | true | Allows carrying identity parameters from the business system to implement password-free login logic |
share_link_expire_time | 86400 seconds | Matches the daily update cycle of daily reports to avoid displaying old data after the link expires |
api_response_cache_ttl | 3600 seconds | Balances the refresh needs of incremental snapshots and interface load, adapting to the 15-minute incremental update rhythm |
share_link_require_password | false | When identity verification parameters are configured, no additional password verification is required to simplify access processes |
iframe_max_height | 1200 pixels | Adapts to the display length of multi-product lists to avoid excessive scrollbars on the page |
The parameter values provided on this page are all common recommended starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis, and it is recommended to test on your own samples before finalizing settings.
Three Common Mistakes
- Symptom: A password input pop-up appears when the embedded page loads for the first time. Cause: Business system identity parameters are not configured, or the
share_link_require_passwordswitch is not disabled, resulting in failed identity verification. - Symptom: The custId parameter cannot be passed after embedding the system, or parameter verification fails. Cause: The
iframe_allow_credentialsconfiguration is not enabled, or the business system does not carry correct identity identifiers in the iframe request. - Symptom: The daily report data displayed on the embedded page has not been updated for more than 24 hours. Cause: The
api_response_cache_ttlconfiguration duration is too long, failing to match the daily update rhythm of daily reports.
How to Verify Successful Configuration
- Open the preset sharing link and check whether the URL contains the expected default parameters such as
dateandproduct_scopefields. - Embed the iframe into the test business system, and verify that no manual password input is required during access, with automatic identity verification completed.
- Wait longer than the configured cache duration, then refresh the embedded page and check whether the data has been updated to the most recent trading day information.
- Open the browser console to confirm there are no cross-domain request errors, verifying that identity parameters are passed normally.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.