API Terms.
Rules designed for both the traditional API and heypster’s decentralized architecture.
1. API license
Subject to the applicable agreement, heypster grants the client a limited, non-exclusive, non-transferable right to access the data and content made available through the API and to display or distribute them within its product in accordance with these terms.
2. Decentralized API and local synchronization
An authorized client may download, store, and serve all or part of the heypster catalog from its own infrastructure when this architecture forms part of its offering or integration.
Under these terms, this storage is not considered merely a temporary cache: it may constitute an operational local library. In return, the client must regularly synchronize with heypster to reflect additions, modifications, removals, delistings, and rights updates.
3. Mandatory removals
When content is removed or marked as unavailable through heypster’s synchronization mechanisms, the client must reflect that change in its local copy within the applicable technical or contractual timeframe. It may not intentionally continue distributing an older version of the catalog in order to circumvent a removal.
4. Catalog integrity
The client must not falsify the origin, rights holder, certification, or essential metadata of any content. Information necessary for heypster Reference GIF and attribution must be preserved when supplied by the API and required by the integration.
5. Permitted uses
The catalog may be integrated into messaging services, keyboards, search engines, applications, platforms, and other approved experiences. Commercial terms, volumes, features, and distribution rights may vary according to the API agreement entered into with heypster.
6. Prohibited uses
It is prohibited to circumvent access controls, falsify synchronization mechanisms, intentionally reintroduce removed content, use the API for illegal activity, or present the heypster catalog as belonging to the client. Standalone resale of API access or the catalog under a third-party brand requires heypster’s authorization.
7. Privacy
The heypster API integration must not be used to turn GIFs, queries, or heypster identifiers into mechanisms for advertising tracking of users. The client remains responsible for its own data processing and regulatory obligations.
8. Security and availability
The client must protect its API credentials and infrastructure. heypster may modify, suspend, or revoke access in cases of abuse, security risk, or contractual violation. Unless specifically agreed in writing, heypster does not guarantee uninterrupted service availability.
9. End of the agreement
When the right to use the API ends, the client must stop new synchronizations and follow the provisions of its agreement concerning deactivation of the integration and the disposition of the local library. Obligations relating to removed content and third-party rights continue to apply.