API Terms

1. Overview

These API Terms govern your use of the Datlyne Data API, the REST interface at www.datlyne.com/v1 that you access with an API key issued against an active subscription. They apply in addition to our Terms of Service and, for the data itself, the Dataset License Agreement: this document covers the mechanics of API access (keys, limits, uptime, versioning); the Dataset License Agreement covers what you may do with the data you retrieve.

Today, the Datlyne Data API is a REST API. Other query interfaces described on our developer pages, such as GraphQL or a direct SQL connection, are planned but not yet available. These Terms will be extended to cover them if and when they ship.

2. API Keys and Confidentiality

Subscribing to a dataset's API issues you a key immediately. Keys come in two environments: live keys, which count against your plan's real usage, and test keys, which are for integration and development and carry lower fair use limits (see the table below).

You are responsible for keeping your keys confidential. Do not publish a key in public source code, client-side application code, a public repository, or any other location a third party could read. You may create additional keys from your account dashboard for your own use, for example one per environment or per internal service, subject to a reasonable limit on the number of active keys per account.

A key inherits its scopes from your active entitlements: it can only query the datasets you are actually subscribed to. If you believe a key has been exposed or compromised, rotate it immediately (see below) or contact support to have it revoked.

3. Fair Use and Rate Limits

Each key is subject to a rate limit (requests per minute), a daily row quota, and a maximum number of rows returned per response. These are enforced in real time; a request past a limit receives a 429 response with a Retry-After header telling you how long to wait.

• Standard plans: 120 requests per minute, 500,000 rows per day, up to 10,000 rows per response (page through more with the cursor the API returns).
• Trial and test keys: 30 requests per minute, 50,000 rows per day, up to 1,000 rows per response.

The daily row quota resets at midnight UTC and is metered per account, not per key. Creating additional keys does not multiply your quota. Consistently running against a ceiling? Contact sales about a higher-volume arrangement; these figures are the fair use limits of our published plans, not a hard ceiling on what Datlyne can support.

4. Key Rotation

You can rotate a key at any time from your account dashboard. Rotating issues a new secret immediately and schedules the old one for retirement. The old secret continues to work for 24 hours after rotation so an in-flight integration does not break the moment you rotate, then it is permanently disabled.

You are responsible for updating your systems with the new secret within that 24-hour window. A key can only have one active predecessor in its rotation chain at a time, so rotating again before the previous grace period ends retires the older secret immediately.

5. Suspension, Revocation, and Subscription End

Datlyne may revoke a key immediately, without prior notice, when:

• The subscription or entitlement that key's scopes depend on ends, lapses, or is refunded. Access is removed the same way whether you cancel or we do.
• You breach the Dataset License Agreement's prohibited uses, including redistributing data obtained through the API.
• We reasonably suspect the key has been compromised, shared outside your organization, or is being used to circumvent rate or quota limits, for example by spreading one workload across many keys or accounts.
• We are required to by law or by a legitimate request from a payment processor or regulator.

Where practical, we will tell you why a key was revoked. Revocation of a key does not, by itself, cancel your subscription or entitle you to a refund; refunds are handled under the Refund Policy.

6. Availability

We target 99.9% uptime for the API, measured monthly against external uptime monitoring. This is a target we manage toward and report on, not a guaranteed service level: we do not currently offer service credits or other compensation for downtime against this target. If we introduce a credited SLA for larger licensing agreements, it will be documented separately and will not apply retroactively.

We will give advance notice of planned maintenance where practical. Unplanned incidents are posted to our status page as we become aware of them.

7. Versioning and Deprecation

The API is versioned; the current version is v1. We will announce a deprecation in the API changelog with a migration window before retiring a version or making a breaking change to an existing endpoint or field. Additive changes, such as new fields, new datasets, or new tables, may ship without advance notice, since they do not break existing integrations.

We recommend pinning your integration to a specific API version in production and reviewing the changelog before upgrading.

8. Data Freshness

Each dataset is refreshed on its own schedule, published on that dataset's page and in the changelog. The API returns the most recently ingested snapshot of a dataset, not a live feed of any real-world source system. There is no real-world source system, since the data is synthetic. Datlyne makes no warranty that data reflects any particular point in time beyond what a dataset's own documentation states.

9. Acceptable Use

In addition to the Dataset License Agreement's restrictions on the data itself, when using the API you agree not to:

• Attempt to bypass or defeat rate limits, quotas, or scope restrictions, including by distributing one workload across multiple keys or accounts.
• Use the API in any way that degrades its availability or performance for other customers.
• Share a key across unrelated organizations, or use one subscription's key to serve customers or clients who are not covered by that subscription's license.

10. Changes and Contact

We may update these API Terms from time to time. Each version carries its own effective date; material changes that reduce your rights will be announced in advance where practical.

Questions about your API access, a key, or these Terms? Reach us through the contact form at datlyne.com/contact. We are happy to help.