ArticleAPI

After the project information is updated, how can API users perform incremental synchronization?

RRootData Editorial Team
Published 5 minUpdated

This article focuses on engineering implementation rather than discussing "whether the data is new." The Synchronous Update (Pro) of the RootData API provides an entry point for discovering changed objects; the product needs to be designed as a stable, rerunnable, and auditable synchronization task to truly enable continuous updates for project pages, financing pages, and person pages.

Treat the RootData update list as a task queue

After periodically querying the update capability, first record the current water level time and the returned entity ID/type, then push objects such as projects, VC, people, or financing into the detail refresh queue. After processing is complete, then advance the water level; do not immediately overwrite the old water level after obtaining the list, otherwise failed tasks will be permanently lost.

Recommended order for incremental synchronization

The first step is to read the changed objects; the second step is to pull the corresponding details by RootData ID; the third step is to compare and write to the local version; the fourth step is to update the search index, cache, and page update time; the fifth step is to record interface failures, null values, and retry results. The synchronization interface is responsible for discovering changes, while field diffs, historical versions, and rollback capabilities should be maintained by downstream systems.

Why retain entity type and source status

The same product may simultaneously display project information, financing records, and personal information. Without entity type and source status, the system cannot determine which type of page should be refreshed, nor can it explain why a certain piece of data has disappeared or changed to a partial status. The entity structure of RootData is suitable for associations, but the local database still needs to maintain its own synchronization logs.

Connecting synchronization with user experience

Do not let users trigger full upstream requests every time they open the page. After the backend completes synchronization, the frontend should display local cache and the last update time; important fields can provide source links. This avoids wasting credits and lets users know which time point the current information corresponds to.

Frequently Asked Questions

Q: Can incremental synchronization replace the initial full import?

A: No. Typically, the initial data setup needs to be completed first, and then the incremental mechanism is used to maintain changes.


Q: Do synchronization interfaces return field differences?

A: It is used to identify changed objects; field-level comparisons and version saving are completed by downstream systems.


Q: How to handle task failures?

A: The water level and failure queue should be retained, and the processing status should be advanced only after a successful retry.


Understanding the RootData API

View API documentation

Related Reading

• How is the data of RootData updated? How should API users understand "freshness"?

• How should the data_status field in financing records be used?

Related content

APIArticle

How does the wallet automatically complete the project background behind tokens?

When wallet users view a token, they usually also need to know which project it corresponds to, who the team members are, whether it has secured funding, or if there are upcoming events. The RootData API can supplement structured data such as projects, individuals, funding rounds, calendars and news to the asset page, enabling wallets to evolve from a "balance and price interface" into a verifiable information portal.

RRootData Editorial Team
5 min
APIArticle

How to choose a Web3 data API: Build, buy, or combine?

Building in-house and procurement are not mutually exclusive. For Web3 products, the real decision is which data must be collected and defined internally, and which structured foundational data is more suitable for direct integration. The RootData API organizes project, financing, investor, person, tag, ecosystem, calendar, leaderboard, and tokenized market data into callable capabilities, reducing the repetitive investment in entity cleaning and relationship maintenance.

RRootData Editorial Team
5 min
APIArticle

When displaying RootData API data to end users, what should be confirmed regarding authorization and signatures?

Displaying API data on web pages, wallets, exchanges, or AI responses is just the first step in technical connectivity. The product also needs to confirm the display range of fields, update and caching rules, source identification, redistribution permissions, and the visible boundaries of user responsibilities, to avoid misunderstanding "can be called" as "can be used freely."

RRootData Editorial Team
5 min
APIArticle

Is the free quota sufficient for testing the RootData API? How can I estimate the usage in a production environment?

The Basic plan of the RootData API currently provides 1,000 Credits per month and a limit of 60 requests per minute, which is sufficient for small-scale field, coverage, and product experience validation; however, it cannot replace production usage assessment. What really needs to be tested is: which RootData data objects are called each time your page or Agent completes a user task.

RRootData Editorial Team
5 min