API Terms of Use

Last updated: 11 July 2026

1. INTRODUCTION AND SCOPE

These API Terms of Use (the “API Terms”) govern your access to and use of the XBXprices Developer API — our REST API that lets registered developers query our compiled Xbox pricing, price-history, sales and catalogue data programmatically (the “API”), as described on our Developer API page and documented in full at /api/v2/docs (together, the “API Documentation”).

The API is a feature of XBXprices.com, operated by Webnetic s.r.o. (“we”, “us”, “our”). Our general Terms of Use (the “Site Terms”) apply to your use of XBXprices.com as a whole, including the API, and are incorporated into these API Terms by reference. These API Terms sit alongside and add detail to Section 9 (Developer API) of the Site Terms; where these API Terms conflict with the Site Terms on a matter specific to the API, these API Terms govern for that matter. Our Privacy Policy and Copyright Policy also continue to apply to any personal data we process about you as a developer and to the underlying rights in Site Content made available through the API.

By requesting, receiving, or using an API key, or by otherwise sending requests to any XBXprices API endpoint, you confirm that you have read, understood and agree to be bound by these API Terms. If you do not agree, you must not request an API key and must not use the API. If you are using the API on behalf of a company or other organisation, you confirm that you have authority to bind that organisation to these API Terms, and “you” refers to both you and that organisation.

2. DEFINITIONS

“API” means the XBXprices Developer API (currently version 2, “v2”), including all endpoints made available under /api/v2/, any earlier or later versions we publish, and any related self-service management endpoints (for example /api/v2/account, /api/v2/account/usage and /api/v2/account/regions). “API Key” means the unique credential issued to you (sent in the X-API-Key request header) that authenticates your requests to the API and ties them to a plan, quota and set of permitted store regions. “API Data” means any price, price-history, sale, discount, catalogue, achievement or other data returned to you through the API. “API Documentation” means the reference material published at /api/v2/docs and on the Developer API page, describing endpoints, parameters, response fields, error codes and plan limits, as we may update it from time to time. “Plan” means the specific tier (for example Free or a paid plan) associated with your API Key, which determines your monthly request quota, page size, permitted store regions, price-history window and whether commercial use and attribution-free use are included, as set out on the Developer API page.

3. ISSUANCE AND SECURITY OF YOUR API KEY

Requesting a key. API access is self-service: you request an API Key by completing the request form at /api-request, describing your project and the plan you want. We review requests by hand and, where approved, issue a key and Plan by e-mail. We may decline, delay or condition the issuance of an API Key at our discretion, including where a request is incomplete, appears to be for a prohibited use under Section 4, or where we are unable to verify the information provided.

Your responsibility for the key. Your API Key is a credential, not a public identifier. You are solely responsible for keeping it confidential and for all activity that occurs through it, whether or not you authorised that activity. You must not publish your API Key in public source code, client-side JavaScript, mobile app binaries, public repositories, forums or anywhere else a third party could extract and reuse it; API calls that touch XBXprices data should be made from your own backend wherever practical. You must not share, sell, sublicense, rent or transfer your API Key to another person or organisation, or use an API Key issued to someone else. If you believe your API Key has been compromised or used without your authorisation, you must notify us immediately at [email protected] so we can rotate or revoke it; we are not liable for any loss or damage arising from your failure to safeguard your API Key.

Our right to rotate or revoke. We may rotate, suspend or revoke any API Key at any time, with or without notice, where we reasonably believe it has been compromised, is being used in breach of these API Terms, or where required for the security or integrity of the Site. Section 8 describes suspension and termination of API access in more detail.

4. ACCEPTABLE USE OF THE API

The API is provided for building applications, websites, dashboards, analytics, bots and user-facing alerts that use API Data as part of a broader product or service. Commercial use requires a paid Plan; the Free Plan is for evaluation and non-commercial projects only, as described on the Developer API page. To keep the API fair, secure and sustainable for every developer, you agree that you will not, and will not attempt to, or assist or permit any third party to:

• exceed, circumvent or attempt to circumvent your Plan’s request quota, page size, region limits or price-history window, including by using multiple API Keys, multiple accounts, or scraping XBXprices.com directly to obtain data beyond what your Plan permits through the API;
• resell, redistribute, sublicense, mirror or bulk-republish raw or lightly-processed API Data to third parties as a standalone dataset or feed, or use API Data to build, train or operate a product or service that directly competes with XBXprices’ core offering (for example, another Xbox price-tracking site, wishlist sale-alert service, or price-history API), without our prior written permission;
• present API Data in a way that misrepresents its source, removes required attribution where your Plan requires it, or otherwise gives the impression that you, rather than XBXprices, are the original source of the pricing, catalogue or achievement data;
• send requests at a volume, frequency or pattern designed to place an unreasonable load on our infrastructure, including denial-of-service-like traffic, aggressive polling that ignores X-RateLimit-Remaining/X-RateLimit-Reset headers, or repeatedly re-requesting data you should instead cache locally, as described in the API Documentation;
• probe, scan or test the vulnerability of the API or any related system, attempt to bypass authentication or rate-limiting, or otherwise attempt to gain unauthorised access to any account, system, server or data;
• use the API, or API Data obtained from it, for any unlawful purpose, or in a way that infringes the intellectual property, privacy or other rights of us or any third party;
• use the API to display, alongside API Data, anything false or misleading about current Microsoft Store prices, availability or purchase terms, or otherwise use API Data in a way likely to mislead end users about a purchase they are about to make.

We reserve the right to investigate suspected violations of this Section, to apply technical measures we consider appropriate to prevent or stop them (including throttling, additional rate-limiting or API Key suspension under Section 8), and to report unlawful activity to the relevant authorities. If you are unsure whether your intended use case is permitted, please ask us first at [email protected] — we would rather clarify in advance than revoke a key after the fact.

5. RATE LIMITS AND FAIR USE

Each Plan carries a monthly request quota and, for list endpoints, a maximum page size, as published on the Developer API page and in the API Documentation; these may change from time to time as we adjust Plans. Quota usage resets at the start of each calendar month (00:00 UTC on the 1st) and is reported on every response via the X-RateLimit-Remaining and X-RateLimit-Reset headers and the meta.rate_limit field, so you can monitor your usage programmatically. Certain self-service management endpoints described in the API Documentation (such as status, account and reference-data endpoints) do not consume quota. Beyond the numeric quota, you must keep your request rate and pattern within what is reasonable for your Plan and use case; we may apply a general, reasonable rate limit to protect the API and other developers even where you have not exhausted your monthly quota, and this limit may change from time to time as our infrastructure and usage patterns evolve. If your use case genuinely needs a higher quota, more regions, or a custom price-history export than any published Plan offers, contact us at [email protected] to discuss a tailored arrangement rather than exceeding your current Plan’s limits.

6. OWNERSHIP OF DATA AND YOUR LICENCE TO USE IT

API Data is derived from our compilation of publicly available information published by Microsoft Store and other public sources, together with data we generate ourselves (such as deal scoring, difficulty ratings and derived analytics). We do not claim ownership of the underlying facts — a game’s price on a given date is not ours to own — but our compiled dataset, its structure, our derived fields and analytics, and the API itself are owned by Webnetic s.r.o. or our licensors and are protected by copyright, database and other intellectual-property laws, as described in Section 7 of the Site Terms. Game titles, cover art, screenshots, publisher and developer names, achievement data and other brand assets returned by the API belong to their respective owners, typically Microsoft, game publishers or developers, and are made available through the API solely for identification and informational purposes.

Subject to your compliance with these API Terms and the limits of your Plan, we grant you a limited, non-exclusive, non-transferable, revocable licence to access and use API Data through your API Key, solely to develop, operate and support your own application, website, service or internal tooling, and to display API Data to your end users as part of that product. No other rights are granted: nothing in these API Terms transfers ownership of API Data to you, gives you the right to redistribute it as a standalone dataset, or grants any licence to our trademarks, logos or brand assets except as expressly permitted for attribution purposes under Section 4 and the Developer API page.

API Data is provided “as is” and is compiled automatically from Third-Party Stores and other public sources. We make no warranty that API Data is accurate, complete, current, or free of errors, and prices, availability, discounts and other details may change or be withdrawn by the Microsoft Store or applicable Third-Party Store at any time without notice and without a corresponding update to the API. If your application displays a price or availability sourced from the API to an end user who is about to make a purchase, you are responsible for making clear that the final price and availability must be confirmed on the applicable store before completing that purchase.

7. SERVICE AVAILABILITY AND CHANGES

We work to keep the API available and performing well, but we do not guarantee, and offer no service-level agreement for, uninterrupted, error-free or continuous availability of the API. The API may be unavailable or degraded from time to time due to planned maintenance, infrastructure issues, upstream data-source outages, security incidents, or factors outside our reasonable control. We may perform maintenance, and may add, change, deprecate or remove endpoints, fields, parameters, error codes, Plans, quotas or other aspects of the API, at our discretion. Where a change is likely to materially affect existing integrations — for example, retiring an API version — we will make reasonable efforts to give advance notice through the API Documentation, the developer dashboard, or e-mail to the address associated with your API Key, and to provide a reasonable transition period where practical, but we are not obliged to maintain any endpoint, field or API version indefinitely.

8. SUSPENSION AND TERMINATION OF API ACCESS

You may stop using the API and let your API Key lapse at any time; if you have a paid Plan billed through a third-party payment processor, cancelling that subscription is handled through the processor as described at checkout. We may suspend, throttle or permanently revoke your API Key and your access to the API, in whole or in part, with or without prior notice, where we reasonably believe that you have breached these API Terms or the Site Terms, exceeded or abused your Plan’s limits, used the API for a prohibited purpose under Section 4, failed to pay for a paid Plan where applicable, or where we are required to do so by law or to protect the security or integrity of the Site. Where practical we will attempt to notify you of the reason at the e-mail address associated with your API Key, but urgent security, legal or abuse-prevention circumstances may require immediate action without prior notice. Sections 6 (Ownership of Data), 9 (Disclaimer of Warranties & Limitation of Liability, as incorporated from the Site Terms) and any other provision which by its nature ought to survive will survive termination of your API access.

9. DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY

The API and all API Data are provided on an “as is” and “as available” basis, without warranties of any kind, whether express, implied or statutory, to the fullest extent permitted by applicable law, exactly as set out in Section 12 (Disclaimer of Warranties) of the Site Terms, which applies to the API in full. The limitation of liability set out in Section 13 of the Site Terms, including its aggregate cap, likewise applies to any claim arising out of or in connection with your access to or use of, or inability to access or use, the API, including any loss arising from incorrect, outdated or unavailable API Data, downtime of the API, a revoked or throttled API Key, or any decision made or action taken by you or your end users in reliance on API Data. Nothing in these API Terms excludes or limits liability that cannot lawfully be excluded or limited, including liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, or intentional misconduct or gross negligence.

10. CHANGES TO THESE API TERMS

We may revise these API Terms from time to time to reflect changes to the API, our Plans, or for legal, regulatory or operational reasons. The “Last updated” date at the top of this page shows when these API Terms were last revised. Where a change is material, we will make reasonable efforts to bring it to your attention, for example through a notice on the Developer API page, the developer dashboard, or e-mail to the address associated with your API Key. Your continued use of the API after a revised version of these API Terms takes effect constitutes your acceptance of the updated API Terms; if you do not agree to the updated API Terms, you must stop using the API.

11. GOVERNING LAW

These API Terms, and any dispute or claim arising out of or in connection with them or the API (including non-contractual disputes or claims), are governed by and construed in accordance with the law of the Slovak Republic, without regard to its conflict-of-law principles, and are subject to the exclusive jurisdiction of the courts of the Slovak Republic, in each case exactly as set out in Section 17 (Governing Law and Dispute Resolution) of the Site Terms, which applies to the API in full and without depriving a consumer of the protection afforded by the mandatory consumer-protection provisions of the law of their country of habitual residence.

12. WHO WE ARE AND API SUPPORT

These API Terms are entered into with .

For API access requests, use the form at /api-request. For questions about these API Terms, your Plan, a suspected breach, or any other API support matter, please write to [email protected] or use our contact page. We aim to respond to API requests within 1–2 business days and will do our best to respond to other queries within a reasonable time.