API Terms and Conditions of Licence and Use

bitfly explorer gmbh, Wiedner Gürtel 9, 1100 Vienna Last updated: 10.12.2025

​

Introduction

(A) The provider operates an application programming interface (“API service”) which registered customers are able to access via the website. The API service is provided for the purposes set out in these Terms and Conditions of Licence and Use. (B) By accessing the API service described below in this document, the customer declares with binding effect that it accepts and will comply with both the General Terms and Conditions and these API Terms and Conditions of Licence and Use. (C) The latest version of these Terms and Conditions of Licence and Use is available on the website https://beaconcha.in/. (D) The API service is intended exclusively for business customers as defined by the Austrian Business Code (UGB). Consumers are excluded from entering into contracts. The customer warrants that it is not a consumer within the meaning of the Austrian Consumer Protection Act (KSchG) and that this is therefore a business transaction for both parties.

​

1. Registration

(1) The customer must have an account in accordance with section 1 of the General Terms and Conditions in order to access and use the provider’s API service. (2) A valid API key is required to use the API service. The customer can access API keys via the user area on the website https://beaconcha.in/. The API key must be stated in the request header with each request in accordance with the provider’s technical API documentation. (3) The user is under an obligation to protect the API key from unauthorised access by third parties and to use it exclusively within the scope of the agreed use.

​

2. API service

(1) The provider currently operates multiple API services: beaconcha.in v1-API as well as beaconcha.in v2-API. (2) A separate API key is required in each case to access the respective API service. API keys for v1-API or v2-API only entitle the user to use the corresponding API version in each case. Reciprocal access to data or functions between the API versions using the same key is not possible from a technical point of view. (3) The customer can order the API service via the website https://beaconcha.in/pricing based on the service packages and prices offered there. The service packages include in each case access to the v1-API as well as the v2-API. (4) The content and scope of the API service are set out in the service specifications for the respective service packages. (5) The provider reserves the right to adjust the scope of the service packages on offer to technological developments, new functions or changes in market conditions at any time. Existing service packages will be assigned to the new service packages that have the corresponding functions. The provider shall be entitled to adjust prices if the cost factors relevant for the provision of services change (in particular staff, infrastructure, energy or licence costs). Price adjustments will be communicated to the customer at least 30 days before these come into effect. The customer will be entitled to terminate the contractual relationship extraordinarily until the increase comes into effect (special right of termination). If the customer does not terminate the contract, the new prices and service content will be deemed to have been agreed. (6) The user may only access the API within the scope of the usage limits and functions provided in the service package. The provider’s record of the API access performed under the respective customer account will be deemed binding unless there is an obvious and demonstrable error in recording this by the provider. (7) Once the usage limit recorded in the service package has been reached or the functional restrictions specified are exhausted, use of the API service will be suspended automatically. The customer may purchase an expanded service package (upgrade) at any time for additional API queries.

​

3. API documentation

(1) The provider will provide the API service specified in the latest applicable API documentation to the customer exclusively for the functionalities specified there, whereby the provider shall be entitled to change and/or adapt the API service at any time. (2) Amendments to the API documentation will be announced on the provider’s website https://beaconcha.in/ and will be considered to be binding from that point onwards. The customer is under an obligation to read the latest applicable version of the published API documentation carefully and apply the same. (3) The provider assumes no responsibility for ensuring that the API documentation provided is compatible with the hardware and software used by the customer.

​

4. API licence

(1) Subject to the provider’s property and exploitation rights to intellectual property in accordance with section 10 of the General Terms and Conditions, the provider grants the customer a non-exclusive, non-transferable, non-sublicensable right that may be revoked at any time to use the API data and/or content provided via the respective API service using an assigned API key. (2) The licence granted is limited to the use specified in the respective service package. The customer may only use the API data and/or content for its own internal business purposes. (3) Any transfer, distribution, publication, sub-licensing, commercial exploitation or other use outside of the purpose of use agreed in accordance with section 4 (2) is prohibited. The customer is prohibited in particular from:

• feeding the API data or parts thereof into third-party databases or setting up an independent database,
• making the data available to third parties – either in return for payment or free of charge,
• removing or modifying references to the origin, copyright or trademark notices.

(4) In the event of a breach of this provision, the provider shall be entitled to block access to the API service at any time with immediate effect and without prior notice. (5) If the customer wishes to use the API data and/or content over and above the usage purpose agreed contractually in accordance with section 4 (2) (in particular integration into external systems, commercial exploitation or use in relation to third parties), a separate written agreement must be entered into with the provider beforehand (e.g. an enterprise subscription or additional licence agreement). Any extended use shall be expressly prohibited until such an agreement has been entered into. Upon request, the provider may submit a corresponding offer to the customer for the extended scope of use. (6) If the customer is granted a licence for transfer or for commercial exploitation of the API data and/or content by means of a separate written agreement in accordance with section 4 (5), then with every use, presentation or transfer of the API data it will be under an obligation to affix a clearly visible designation with the notice “Powered by beaconcha.in” and the logo provided by the provider in accordance with the branding guidelines. The provider shall be entitled to review compliance with these labelling requirements at any time. (7) Any use of the API content that exceeds the licence and usage rights expressly granted herein is prohibited. (8) The customer will retain its property rights to the data content that it makes available to the provider for use in connection with providing the API service. The customer will grant the provider in this regard a non-exclusive, non-transferable right to use the data content made available by the customer exclusively for the customer’s benefit for fulfilment of the provider’s obligations under these Terms and Conditions of Licence and Use.

​

5. Unauthorised use

(1) The customer makes the following undertakings in connection with the use of the API service:

• not to use the API service in any way that violates applicable law, including but not limited to the intellectual property rights, unfair competition rights and personal rights of third parties;
• not to use the API service for unlawful, abusive or fraudulent purposes;
• to present its own identity truthfully and not to conceal the same;
• not to transfer the API keys to third parties or make them available to the public;
• to keep its access data and API keys secret;
• not to reproduce, replicate, modify or redesign API content, transfer it to third parties, make it available to the public or create derivative works from it;
• not to use API content to operate competing or proxy API services;
• to refrain from having reverse engineering operations implemented, scraping data or attempting to circumvent rate limitations or authentication systems;
• not to implement any measures that could adversely affect the API service or infrastructure of Bitfly or other users.

(2) The customer will be under an obligation to notify the provider without delay of any suspicion that its access data, API keys and/or other confidential information in connection with the use of the API service could have become known to unauthorised third parties. (3) The provider shall be entitled to block access to the API service in the event of a breach of these Terms and Conditions of Licence and Use by the customer or third parties attributable to it. The access will only then be restored once the breach has been permanently remedied or the risk of recurrence has been eliminated through submission of a corresponding declaration to cease and desist.

​

6. Payment terms

(1) Use of the API service is subscription-based. The prices applicable in each case for the service packages are available on the provider’s website at https://beaconcha.in/pricing. All prices are quoted in euros, plus statutory VAT, unless otherwise stated. (2) The provider uses the external payment service provider “Stripe” (Stripe, Inc., 354 Oyster Point Blvd, South San Francisco, CA 94080, USA) for billing of subscriptions. By using the services, the customer agrees that payment details will be processed in accordance with Stripe’s terms and conditions of use and privacy policy. The payment details entered will be processed directly by Stripe and not be stored by the provider. (3) Payments can only be made by credit card or via another payment method supported by Stripe. The provider will not be liable for failures or errors in the payment processing by Stripe unless these are attributable to gross negligence or wilful intent on the part of the provider. (4) Customers may change their requested service package at any time within their account:

• Upgrade: the difference is calculated immediately and the new plan will apply from the time of the change.
• Downgrade: a downgrade in the subscription will take effect from the start of the next billing period. If there is a credit balance remaining in the assigned Stripe account following the downgrade, this balance will automatically be offset against future charges until it has been consumed in its entirety. Any payments already made will not be reimbursed.

(5) The subscription will start as of the date that the customer selects the requested service package and billing period, and will renew automatically until it is cancelled. The subscription fee will be debited automatically from the credit card stored in the customer’s Stripe account in each case on the payment date shown in the customer’s Stripe account. (6) In the event that the contractual relationship is terminated by the customer (see section 9), there will be no pro rata refund of amounts already paid for the relevant service period.

​

7. Exclusion of liability

(1) The provider does not warrant that the API service will be fully functional at all times and without interruptions. The provider therefore does not provide any warranties, guarantees and/or assurances of success of any kind whatsoever with regard to the API service, particularly with respect to the particular suitability of the API service and/or the API content for a specific purpose; the API content is provided to the customer “as is” without any express or implied warranty. The provider is in particular under no obligation to review the results (API data and/or content) from the use of the API service for legality, accuracy or completeness. (2) Furthermore, the provider assumes no responsibility for circumstances that are within the customer’s sphere of influence, particularly with respect to its hardware, software or internet connection. (3) In the event of a separate agreement regarding the availability of the API service (Service Level Agreement, “SLA”), the service levels guaranteed there with respect to guaranteed availability, response times and recovery times will apply. If no such agreement is in place, the provider will assume no warranty for uninterrupted availability of the API service.

​

8. Compensation and limitation of liability

(1) Use of the API is at the customer’s own responsibility and at its own risk. The customer will be responsible exclusively for any damage resulting from the use of the API service, including any damage to the customer’s own IT system or loss of data. (2) The provider will be liable in accordance with the statutory provisions exclusively for damage caused intentionally or through gross negligence by the provider and its vicarious agents. The provider’s liability is excluded for damage that is not typical for this type of contract, for consequential damage, in particular lost profits and lost savings, and for pure financial losses, except in cases involving wilful intent on the part of the provider. The customer’s claims will expire within six months of becoming aware of the damage and of the party at fault.

​

9. Duration of the API service

(1) The customer shall be entitled to cancel the subscription directly at any time via the Stripe customer portal. In this case, the subscription will end automatically at the end of the current billing period. Any payments already made for the current billing period will not be reimbursed. (2) If the customer downgrades to a cheaper tariff during a current billing period, a pro-rata credit note for the amount already paid will be issued to the assigned Stripe account (see section 6 (4)). (3) The provider will be entitled to suspend or block access to the API service for cause, particularly if the customer:

• has provided false customer details or access to the API service has been obtained by other fraudulent means;
• has disclosed the access details to unauthorised persons and/or the API service is used in breach of the agreement;
• fails to comply with any other essential provision in these Terms and Conditions of Licence and Use for the purposes of section 5 and fails to comply with these despite being requested to remedy the breach of contract or defaulting situation within a grace period of seven calendar days.

(4) The contracting parties will be entitled to terminate the API service immediately if the API service is unavailable for more than 90 days due to force majeure. Any amounts already paid for services not rendered will not be reimbursed unless otherwise agreed.

​

10. General provisions

(1) These API Terms and Conditions of Licence and Use shall take precedence over the provider’s general terms and conditions. Unless specified otherwise in these API Terms and Conditions of Licence and Use, the provider’s general terms and conditions shall apply. (2) We shall be entitled to amend, supplement or replace these terms and conditions at any time. We will notify you of any changes via e-mail. You will have 14 days to object to the changes after receiving the notification. If no objection is stated within this period, the changes shall be deemed to have been accepted by you. We will inform you in the notification email that any failure to exercise your right of objection will be deemed to constitute consent.

​

Document History