API Terms
Last updated: 17 November 2026 (version 2026-11-17)
On this page
These API Terms apply to the Kukie.io API, which Pixadoro Ltd., Blvd. Cherni Vrah 47, 1407, Sofia, Bulgaria, company number 206777328 (“Company”, “we”, “us”, “our”) provides to its customers (“Customer”, “you”, “your”).
You accept these API Terms when you create an API Key. They add to our Terms of Service, Privacy Policy and Data Processing Agreement, which continue to apply to everything you do with the API. Words defined in the Terms of Service have the same meaning here. Where these API Terms and the Terms of Service differ on the use of the API, these API Terms prevail.
1. Definitions
- “API” means the Kukie.io application programming interface at https://api.kukie.io, every version of it we make available, and its documentation.
- “API Key” means a secret credential that starts with
kk_live_, which we issue to an Organisation for the API. - “API Customer” means a Customer whose Plan includes API access and who has created an API Key.
- “Your Clients” means the businesses and people for whom you use the API to provide your own products or services.
2. Access to the API
- The API is available to Organisations whose Plan includes API access, or under a separate written agreement with us. An API Key cannot be created or replaced while the Organisation is on a free trial.
- Only the owner and the admins of an Organisation can create API Keys.
- An API Key belongs to the Organisation, not to the person who created it. It keeps working when that person leaves the Organisation, until it expires or is revoked, or, if you replace it with a new API Key (roll it), until the end of the grace period you choose.
- When you create an API Key, you choose what it may do (its permissions) and which Sites it can reach: every Site of the Organisation, including Sites added later, or the Sites you select. Every request is checked against them, and an API Key never reaches another Organisation's Sites. An API Key expires after the period you choose, never more than 365 days.
- If your Plan stops including API access, requests made with your API Keys are refused until it includes it again. A request for your account details still answers, so your systems can see why.
3. Your API Keys and Your Responsibilities
- You are responsible for keeping your API Keys secret and for every request made with them, as for all activities under your account (clause 3.2 of the Terms of Service).
- Send an API Key only in the Authorization header of a request to the API. Never put one in a web page, a browser script, a mobile app, a public code repository or a link, and never share it with another Organisation. We refuse a request that carries an API Key in its query string.
- If you think an API Key has been exposed, revoke it at once and tell us at support@kukie.io.
- Some text in API responses comes from websites we scanned or from visitors to your Sites, and is marked as such. We do not check it, so escape it before you show it in a web page or another program.
- You confirm that you own every domain you add through the API, or have the right to add it, to configure Kukie.io for it and to ask us to scan it (see also clauses 2.4 and 9.3 of the Terms of Service). When you scan a Site, our scanner visits its pages. A scan started through the API follows the Site's robots.txt file, and may visit fewer pages or none, unless one of our scans has recently found that Site's Kukie.io script installed on it.
4. Using the API for Your Own Clients
You may use the API to build and run your own products and services for Your Clients, including managing Your Clients' websites through Kukie.io and showing information from the API in your own product, as long as:
- each of Your Clients' websites is a Site in your Organisation, within the limits of your Plan;
- you remain our Customer and are responsible to us for every Site and for every use of your API Keys;
- Your Clients do not receive your API Keys; and
- you do not offer Kukie.io, the API or access to them to anyone as a product in its own right.
The branding rules of clause 4.9 of the Terms of Service apply to the banners on those Sites. Where you act for Your Clients as their processor, clause 2.2 of the Data Processing Agreement applies.
This section is our written consent under clause 13(8) of the Terms of Service for the use it describes.
5. Fair Use and Rate Limits
- Each API Key and each Organisation can make a limited number of requests in a given time. The limits are published in the API documentation and may change. A request over a limit is refused with an answer that says when to try again.
- Do not try to get around the limits, for example by spreading requests over several API Keys or Organisations, and do not send requests that put an unreasonable load on the Services.
6. Suspending an API Key
- We may suspend or revoke an API Key, or limit the requests made with it, without suspending the rest of your account, if we reasonably believe it has been exposed or is used by someone who should not have it, if its use breaches these API Terms or the Terms of Service or puts the security or availability of the Services or of other customers at risk, or if the law requires it.
- We will tell the owner and the admins of your Organisation by email without undue delay, and say why, unless the law or the security of the Services prevents it.
- Clause 8.3 of the Terms of Service continues to apply to your account as a whole.
7. Availability
- We provide the API on a best-effort basis. We work to keep it available and fast, but we make no commitment to any level of availability or response time for the API, and the availability stated in clause 2.3 of the Terms of Service does not apply to it. A service level for the API applies only where it is set in a separate written agreement signed by you and us.
- Clauses 9 and 10 of the Terms of Service (warranties, disclaimers and limitation of liability) apply to the API. The API is a tool: using it is not legal advice and does not by itself make a website meet the requirements of any law (clause 2.2 of the Terms of Service).
8. Changes to the API
- The version of the API is part of every address, for example
/v1. Within a version we may add endpoints, fields, values and optional parameters at any time, so build your software to ignore fields and values it does not know. - A change that could break software built for a version, such as removing or renaming an endpoint or a field, changing what a field means, or retiring the version, takes effect only after at least 12 months' notice. We give that notice in the responses of the affected endpoints (with Deprecation, Sunset and Link headers), in the API changelog, and by email to the owner and the admins of every Organisation whose API Keys called an affected endpoint in the 90 days before the notice. New behaviour that would break software is otherwise offered only in a new version.
- If we must change the API sooner to fix a security problem or to comply with the law, we will give as much notice as we can and tell you why.
9. Data Protection
When you use the API, we process the data described in our Privacy Policy, including the records of API Keys and API requests in section 8.9. Consent records and consent figures your systems read through the API are processed under our Data Processing Agreement (Annex I, item 9): we act as your processor, and the systems that receive them are yours or ones you choose, not our sub-processors.
10. Ending the Use of the API
- You can stop using the API at any time by revoking your API Keys. A revoked or expired API Key stops working at once, and a replaced API Key at the end of its grace period.
- Deleting your Organisation, or the account of the person who owns it, deletes its API Keys.
11. Changes to These API Terms
- We may change these API Terms. The date and version at the top of this page show which text is current, and each API Key records the version accepted when it was created.
- We will tell the owner and the admins of every Organisation that holds an active API Key by email at least 30 days before a change that reduces your rights takes effect, as clause 15 of the Terms of Service does for the Terms. If you do not agree, revoke your API Keys before the change takes effect; using the API after that date means you accept it.
12. Contact
If you have any questions about these API Terms, please contact us at:
Pixadoro Ltd.
Blvd. Cherni Vrah 47, 1407, Sofia, Bulgaria
Email: support@kukie.io
Website: kukie.io
