Supplementary Terms for the Dealer API (Draft)

1.1These terms apply in addition to the Terms of Service to the use of the FurtherSales Network Dealer API by commercial dealers (creating, updating, reporting sales of, withdrawing and reactivating machines, and retrieving the inventory overview through the technical interface).

1.2The technical description of the interface is set out in the current API documentation. Without an express agreement it does not create additional commitments regarding performance or availability.

1.3In the event of conflict, these terms take precedence over the Terms of Service as regards use of the API.

1.4Use of the API under these terms for the dealer’s own dealer profile is not unauthorised scraping within the meaning of Section 19 of the Terms of Service.

1.5Language versions: these terms are intended to be provided in full in German and English. In the other platform languages, a localised notice referring to the English version is shown.

2.1The API is available only to dealers with a FurtherSales dealer profile who have themselves enabled API access for their profile and, once the consent function is switched on, have accepted these terms (§ 11).

2.2No separate fee is charged for using the Dealer API; it is included in the existing dealer offering. Fees agreed for the respective dealer offering remain unaffected.

2.3There is no entitlement to particular additional functions, individual adjustments or a permanently unchanged scope of service.

2.4The API may only be used to manage machines and content that the dealer is entitled to market.

3.1The dealer may engage external software providers, inventory-management providers or IT integrators to connect to the Dealer API.

3.2The service provider acts on behalf of the dealer and with the dealer’s access. The dealer ensures that the service provider complies with the security requirements and usage restrictions of these terms.

3.3Engaging a service provider does not, by itself, create a contractual relationship between FurtherSales and the service provider. FurtherSales does not initially enter into a separate agreement with the service provider.

3.4Passing the access on to other third parties is not permitted.

4.1Access is provided through an individual API key assigned to the dealer profile. The key is generated in the dealer area and is shown only once. FurtherSales does not store it in plain text and cannot display it again.

4.2The dealer keeps the key secret: only on its own servers or on servers of providers it has engaged, and not in browser code, mobile apps, source-code repositories, tickets, e-mails or chats.

4.3Authentication uses the HTTP header “Authorization: Bearer” with the key. Transmitting the key in the request body, which is still accepted for a transition period, will be phased out; its use is not recommended.

4.4If there is a suspicion that a key has become known to unauthorised persons, the dealer immediately rotates or deactivates the access in the dealer area and informs FurtherSales at partners@furthersales-network.com. After a rotation, the old key is invalid.

4.5Responsibility for actions taken with the dealer’s key depends on cause and fault and on § 10. A blanket assumption of liability by the dealer for every security incident is not intended.

4.6FurtherSales may block a key or deactivate access if there is a suspicion of misuse or a security concern (§ 8).

5.1The dealer is responsible for the accuracy, completeness, currency and lawfulness of content submitted through the API (see Sections 3 and 14 of the Terms of Service). This includes in particular technical data, prices, currencies, availability, sales status, descriptions and images. Responsibility for errors of the software or service provider used is governed by § 10.

5.2The dealer ensures that it holds the necessary rights to texts, images and other content. Images are submitted as web addresses and remain on the dealer’s server; the dealer keeps them accessible for as long as the listing is published.

5.3Free-text fields (e.g. description, known defects) must not contain personal data of third parties for whose publication the dealer has no legal basis.

5.4Status of new machines: machines created through the API are created as drafts by default. If the request so specifies, and subject to the platform’s publication check, a machine can also be published directly. If the publication check is not passed, publication is not carried out. FurtherSales may continue to review, restrict or remove content under the Terms of Service (Sections 3 and 4). Publication through the API does not create a right to publication.

5.5Technical acceptance by FurtherSales is not a review of, or confirmation of the accuracy of, the content. FurtherSales gives no warranty that submitted data is accepted without error. The dealer checks the accepted data in the app.

5.6The dealer reports sold machines as sold without undue delay.

5.7A machine reported as sold cannot be published again through the API. Data may still be corrected as long as no status change is sent.

5.8If a sale falls through, the dealer can take the machine back into stock by explicitly reactivating it. It then becomes a draft and is not public. The dealer checks the data before publishing again. (“Reactivation” here refers to the machine, not to API access; for access, § 11 “activation” applies.)

5.9The particularities described in the API documentation apply to archived machines and to machines maintained through an inventory feed. FurtherSales does not provide a history of status changes and makes no commitment to retain such histories.

6.1The API may only be used within its intended functionality, for the dealer’s own dealer profile and for machines the dealer may dispose of.

6.2In particular, the following are not permitted: circumventing or impairing technical safeguards, trying other parties’ keys, accessing other dealers’ data, sending requests in a way that may impair the operation of the platform, and submitting conflicting changes to the same machine in parallel. Requests concerning the same machine must be sent one after another.

6.3FurtherSales may introduce technical safeguards and reasonable restrictions to ensure stable and secure operation. Request limits (rate limits) are currently not defined.

6.4The API may be further developed or changed. There is currently no version number for the interface; no test environment (sandbox) is provided.

7.1The Dealer API is provided within FurtherSales’ technical and operational capabilities. Section 20 of the Terms of Service applies to availability.

7.2No minimum availability, service levels (SLA) or fixed processing, recovery or support response times are promised.

7.3Temporary restrictions may occur in particular because of technical faults, security measures, maintenance or further development. Support requests can be sent to partners@furthersales-network.com.

8.1The dealer can deactivate API access or rotate the key at any time in the dealer area.

8.2FurtherSales may restrict, block or terminate API access in the event of a breach of these terms or the Terms of Service, in the event of a concrete suspicion of security issues or misuse, if platform operation is impaired, and in the cases described in Section 22 of the Terms of Service. The dealer will be informed to the extent this is reasonable and compatible with security interests.

8.3API access becomes ineffective when the dealer relationship ends. The relationship ends upon effective termination or authorised deletion of the dealer account or profile; mere inactivity does not end it automatically. The associated access data is deleted by authorised FurtherSales staff in a documented, regulated procedure.

8.4Listings that are already published are not changed automatically by the end of API access; Section 22 of the Terms of Service remains unaffected.

9.1For security and traceability purposes, FurtherSales logs security-relevant events in API key management, in particular creation, rotation, activation and deactivation of access, with the time, the acting user and the dealer profile. The key, its hash and the key prefix are not part of these log entries. Access is restricted to authorised FurtherSales administrators.

9.2FurtherSales processes the access and usage data required to provide and secure the Dealer API. Details are set out in the Privacy Policy.

9.3The dealer is responsible for the lawfulness of personal content it submits, to the extent this responsibility rests with it under applicable law. Responsibilities for data submitted through the API are to be clarified separately.

9.4A purpose-bound deletion concept applies to access data, logs and records of consent. No retention periods have been set.

10.1Liability is governed by the validly agreed general Terms of Service (Section 21), to the extent permitted by law and where no more specific rule is required.

10.2Liability in connection with the API depends on cause, fault and an effective contractual allocation of risk. A blanket assumption of liability by the dealer for every security incident is not intended.

11.1When: the dealer accepts these terms in the dealer area (a) before an API key is generated, (b) at every key rotation and (c) when a deactivated API access is activated.

11.2When not: no acceptance is required for deactivating an access, for individual API calls, for an access that is already active, for reading data, or for changes to the default currency. Deactivation is possible at any time regardless of consent and logging errors.

11.3Who: the consent comes from the dealer. Technically, only the owner of the dealer profile can consent for their own profile. FurtherSales administrators do not give consent on behalf of dealers and cannot replace missing consent.

11.4Evidence: FurtherSales stores the consent on the server together with the version of the terms, the version of the Privacy Policy, the time, the dealer profile, the consenting user and the wording of the consent statement shown. Repeated consent to the same version does not create further evidence.

11.5Consequence of missing consent: if consent is missing or cannot be checked or stored, the generation, rotation or activation is not carried out; the previous state remains unchanged and a previous key remains valid.

11.6Existing accesses: existing accesses are retained; running API calls are not interrupted. Consent is first requested at the next generation, rotation or activation. There is no fixed cut-off date; a transition process communicated separately applies to existing accesses. External productive use without verifiable consent has not been released.

11.7Changes: for a new version of the terms, consent is requested again at the next generation, rotation or activation. Changes are announced through a suitable communication channel.

12FurtherSales GmbH. API and partner enquiries: partners@furthersales-network.com. Access credentials, in particular the API key, must never be sent by e-mail.