API Terms of Use

1. What the API provides

The API provides read-only data from the RusLit catalog: literary eras, authors and works with their cards (annotation, creation history, context, facts) in the available languages, tables of contents (chapter numbers and titles), covers and information about the text source.

The full texts of works are not available through the API. The site shows texts to readers, but that is not a permission to obtain them programmatically: see section 4.

2. Access

• Requests are submitted by site users with a confirmed email address. Access is opened only by a RusLit administrator after review; the operator may decline a request without giving reasons.
• The first approval grants access for 6 months, each extension for 12 months. The partner receives an email 30 and 7 days before access expires; extensions are granted on the partner's request.
• The app secret is shown once. The partner keeps it confidential, does not publish it in code and does not ship it to a browser or mobile app. If the secret may have leaked, the partner immediately creates a new one on the app page.
• The partner is responsible for all requests made with the secret of their app.

3. Attribution

When showing catalog data, the partner credits the source: "Data: RusLit" with a link to the page of the work, author or era on the RusLit site (links are provided in API responses, field siteUrls).

Every cover has its own source and license (field cover.source): the partner shows them next to the image or on a details page and follows the terms of that license.

The partner must not suggest that RusLit endorses or is affiliated with the partner's product unless agreed in writing.

4. What is allowed and what is not

Allowed:

• showing catalog data to the users of the partner's product with attribution;
• keeping a copy of the data and refreshing it at least [EVERY 30 DAYS] (parameter updatedSince);
• [COMMERCIAL USE - TO BE DECIDED BY COUNSEL].

Not allowed:

• obtaining the texts of works programmatically from the RusLit site (scraping the reader or the site API) or by any other means that bypass this API;
• selling or passing catalog data to third parties as a standalone dataset;
• circumventing rate limits, including by using several apps or keys for one integration;
• distorting work cards or presenting them as the partner's own text;
• using the API for actions that violate the law or the rights of third parties.

5. Limits and availability

Rate limits depend on the app tier: basic - 60 requests per minute and 10,000 per day, extended - 600 per minute and 200,000 per day. The tier is set by an administrator; when a limit is exceeded, the API responds with status 429.

The API is provided "as is", without availability guarantees or a service level agreement unless agreed separately. The operator may temporarily restrict access for maintenance and to protect the service.

6. API versions

The version is part of the URL (/api/partner/v1). Version 1 only receives compatible changes: new endpoints, optional parameters and response fields. The partner ignores fields they do not know.

Incompatible changes are released as a new version; the previous version keeps working for at least 6 months after that. The operator informs owners of active apps about a new version by email.

7. Suspension and revocation

The operator may suspend or revoke an app's access if these terms are violated, if security is at risk or if the load interferes with the site. The reason is sent to the app owner by email. When access is suspended, issued tokens stop working immediately; revoked access cannot be restored, but a new request can be submitted.

The partner may stop using the API at any time.

8. Partner data

The operator processes the app owner's data (name, email, organisation, app details) and the app's request statistics as described in the privacy policy (section on API partners). No data about site readers is shared through the API.

9. Liability

[LIMITATION OF THE OPERATOR'S LIABILITY - TO BE DECIDED BY COUNSEL]. The partner is responsible for how the data is used in their product and for complying with cover licenses.

10. Changes to these terms

The operator informs app owners by email about a new version of these terms at least [30 DAYS] before it takes effect. By continuing to use the API after that, the partner accepts the new version.

11. Governing law

[GOVERNING LAW AND DISPUTE RESOLUTION - TO BE DECIDED BY COUNSEL].

12. Contacts

Questions about access, extensions and rate limit tiers: [PARTNER EMAIL]. Operator: [OPERATOR NAME], [OPERATOR ADDRESS].