Skip to main content
All CollectionsROOK Connect
Frequently Asked Questions (FAQ) for the Pre-existing Data
Frequently Asked Questions (FAQ) for the Pre-existing Data

Get answers to common questions about the Pre-existing Data feature.

Paola Malo Molina avatar
Written by Paola Malo Molina
Updated over a week ago
  1. Will I need to set up an additional endpoint?

    No, additional endpoints are not required. Once the Pre-existing Data feature is activated, historical user data will be sent automatically through the Data Webhook.

  2. What is the format of the JSON files for historical data?

    The JSON files for historical data follow the same structure as those used for daily data deliveries, ensuring seamless integration with your existing workflows.

  3. Is the data extraction process automatic or manual?<


    The data extraction process is fully automatic. Once Pre-existing Data is enabled, historical data is automatically retrieved and sent via your configured webhook.

  4. How is user privacy ensured when accessing historical data?

    ROOK complies with privacy and security regulations, such as GDPR and HIPAA. Historical data is only accessed and processed with the user's consent, and all data is encrypted during transmission and storage.

  5. What data sources are supported for Pre-existing Data?

    The Pre-existing Data feature is compatible with the available data sources, including:

  6. Can I disable Pre-existing Data after enabling it?

    Yes, you can disable Pre-existing Data at any time by revisiting the Customize ROOK module in your account settings. Data retrieval and processing will stop immediately upon deactivation.

  7. What happens if my webhook is misconfigured when Pre-existing Data is enabled?

    If the webhook is misconfigured, historical data cannot be delivered until the issue is resolved. Ensure that your webhook is correctly configured in the settings to avoid disruptions.

  8. Can I selectively retrieve data for specific users?

    No, Pre-existing Data is automatically retrieved for all connected users as part of the feature. However, you can manage data retention and processing through your backend systems.

  9. Does enabling Pre-Existing Data affect the performance of daily data deliveries?

    No, enabling Pre-Existing Data does not affect the performance of daily data deliveries. Historical data is processed separately and delivered via the same webhook, ensuring efficient handling of all data.

  10. Can I use Pre-existing Data to calculate custom health metrics?

    Yes, you can use the retrieved historical data to calculate your own health metrics. However, this requires implementing your own analytics or using the ROOKScore alongside the feature.

  11. What happens if the user’s health data source does not support historical data?

    If a user's data source does not support historical data, no data will be retrieved for the Pre-existing Data feature. However, daily data deliveries will continue as usual once the connection is established.

  12. Is there a sandbox environment for testing Pre-existing Data?

    Yes, ROOK provides a sandbox environment where you can test the Pre-existing Data feature. Contact our Support Team to get access to the sandbox environment.

  13. What type of data is included in the Pre-existing Data feature

    The Pre-existing Data feature includes:
    - Physical Summary
    - Sleep Summary
    - Body Summary
    - ROOKScore (sent within 24 hours of linking)

  14. When is Pre-existing Data sent to the webhook?

    Pre-existing physical, sleep, and body information is sent immediately after the user links their account. The ROOKScore is guaranteed to be sent within 24 hours of the user linking.

  15. What if the data source is not synchronized?

    If the data source is not synchronized or the user has not accessed the application recently, Pre-Existing Data cannot be extracted.

  16. How is the most recent body information handled?

    For Body information, the last update made by the user in their data source is always sent.

Did this answer your question?