Dynamic content for a token platform
Abstract
Methods, systems, and devices for data management are described. A presentation service may receive an application programming interface (API) request to generate a first update to a content item for display at a client application. The presentation service may cause, based on receiving the API request, the first update to the content item to be displayed at the client application. The presentation service may synchronize the first update to the content item to a content management system. A service may transmit, to the content management system, a second update to the content item that is synchronized to the content management system. The presentation service may cause, based on transmitting the second update, the second update to the content item to be displayed at the client application.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method for data management, comprising:
receiving an application programming interface (API) request to generate a first update to a content item for display at a client application: causing, based at least in part on receiving the API request, the first update to the content item to be displayed at the client application: synchronizing the first update to the content item to a content management system: transmitting to the content management system, a second update to the content item that is synchronized to the content management system; and causing, based at least in part on transmitting the second update, the second update to the content item to be displayed at the client application.
2 . The method of claim 1 , wherein causing the first update or the second update to the content item to be displayed at the client application comprises:
causing the first update or the second update to be stored in a storage location from which the client application pulls information.
3 . The method of claim 1 , wherein receiving the API request comprises:
receiving the API request that defines a container user interface for displaying the content item.
4 . The method of claim 3 , wherein transmitting the second update to the content item comprises:
transmitting the second update to the content item that is to be displayed within the container user interface.
5 . The method of claim 1 , wherein causing the first update or the second update to be displayed at the client application comprises:
selecting the content item from a plurality of content items based at least in part on one or more selection criteria.
6 . The method of claim 5 , wherein the one or more selection criteria are based on a content type or user attributes.
7 . The method of claim 5 , further comprising:
determining a ranking for the content item using one or more machine learning algorithms, wherein the content item is selected based at least in part on the determined ranking for the content item.
8 . The method of claim 1 , wherein the content item is configured to obtain a current characteristic associated with a crypto token when pulled by the client application for display via the client application, and wherein the content item is configured to display, at the client application, an indication of the current characteristic.
9 . An apparatus for data management, comprising:
one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the apparatus to:
receive an application programming interface (API) request to generate a first update to a content item for display at a client application;
cause, based at least in part on receiving the API request, the first update to the content item to be displayed at the client application:
synchronize the first update to the content item to a content management system:
transmit to the content management system, a second update to the content item that is synchronized to the content management system; and
cause, based at least in part on transmitting the second update, the second update to the content item to be displayed at the client application.
10 . The apparatus of claim 9 , wherein, to cause the first update or the second update to the content item to be displayed at the client application, the one or more processors are individually or collectively operable to execute the code to cause the apparatus to:
cause the first update or the second update to be stored in a storage location from which the client application pulls information.
11 . The apparatus of claim 9 , wherein, to receive the API request, the one or more processors are individually or collectively operable to execute the code to cause the apparatus to:
receive the API request that defines a container user interface for displaying the content item.
12 . The apparatus of claim 11 , wherein, to transmit the second update to the content item, the one or more processors are individually or collectively operable to execute the code to cause the apparatus to:
transmit the second update to the content item that is to be displayed within the container user interface.
13 . The apparatus of claim 9 , wherein, to cause the first update or the second update to be displayed at the client application, the one or more processors are individually or collectively operable to execute the code to cause the apparatus to:
select the content item from a plurality of content items based at least in part on one or more selection criteria.
14 . The apparatus of claim 13 , wherein the one or more selection criteria are based on a content type or user attributes.
15 . The apparatus of claim 13 , wherein the one or more processors are individually or collectively further operable to execute the code to cause the apparatus to:
determine a ranking for the content item using one or more machine learning algorithms, wherein the content item is selected based at least in part on the determined ranking for the content item.
16 . The apparatus of claim 9 , wherein the content item is configured to obtain a current characteristic associated with a crypto token when pulled by the client application for display via the client application, and wherein the content item is configured to display, at the client application, an indication of the current characteristic.
17 . A non-transitory computer-readable medium storing code for data management, the code comprising instructions executable by one or more processors to:
receive an application programming interface (API) request to generate a first update to a content item for display at a client application: cause, based at least in part on receiving the API request, the first update to the content item to be displayed at the client application: synchronize the first update to the content item to a content management system; transmit to the content management system, a second update to the content item that is synchronized to the content management system; and cause, based at least in part on transmitting the second update, the second update to the content item to be displayed at the client application.
18 . The non-transitory computer-readable medium of claim 17 , wherein the instructions to cause the first update or the second update to the content item to be displayed at the client application are executable by the one or more processors to:
cause the first update or the second update to be stored in a storage location from which the client application pulls information.
19 . The non-transitory computer-readable medium of claim 17 , wherein the instructions to receive the API request are executable by the one or more processors to:
receive the API request that defines a container user interface for displaying the content item.
20 . The non-transitory computer-readable medium of claim 19 , wherein the instructions to transmit the second update to the content item are executable by the one or more processors to:
transmit the second update to the content item that is to be displayed within the container user interface.Join the waitlist — get patent alerts
Track US2025110804A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.