API and integration terms

Version 1.0 – Last updated: 26 October 2026

These terms (“API Terms”) apply when you, as customer or integration partner (“API Consumer”), are granted access to DigiQuip APIs, including the Registry API with machine-to-machine (M2M) credentials, webhooks, and other programmatic interfaces that DigiQuip issues in writing.

The API Terms are a supplement to the agreement between the parties. They complement, and do not limit, the General Terms, the EULA where relevant to end users, and any main agreement, data processing agreement, and service description between the API Consumer and DigiQuip AS (org. no. 923 673 911) (“DigiQuip”). If the API Terms conflict with the main agreement, the main agreement prevails unless the API Terms expressly take precedence for API use.

By using API access or continuing to call the API after updated terms are published, the API Consumer accepts the API Terms.

1. Scope and definitions

API access covers use of issued credentials (for example M2M client ID and secret), access tokens, API keys, permitted organization IDs (allowed_organizations), and documented endpoints in the environment DigiQuip has opened (test, production).

Registry data means data stored or changed in the DigiQuip Registry and related catalogs (for example assets, asset types, identifiers, brand and model catalog) that the API Consumer reads or writes via the API.

Faulty or harmful API use includes, without limitation: calls outside issued scopes; bulk or disproportionate creation of duplicates; writes to the shared catalog (brand/model) contrary to DigiQuip guidelines; deletion, merge, or changes that disrupt other customers or end users; using test against production data or vice versa; attempts to bypass rate limits, security, or audit; and integration logic that systematically introduces incorrect or incomplete registry data.

2. API Consumer obligations

The API Consumer shall:

• Use the API only for purposes agreed with DigiQuip and within issued scopes and organization limits.
• Follow official documentation, the OpenAPI specification for the relevant environment, and DigiQuip integration guidelines (for example search-first in the brand/model catalog, limited use of create where agreed).
• Protect credentials and tokens; not share secrets in source code, logs, or public repositories.
• Test changes in the test environment before production where DigiQuip provides a test environment.
• Notify DigiQuip without undue delay if credentials may be compromised, unintended bulk writes occur, or data quality issues are caused by the integration.

The API Consumer is responsible for its own software, scheduled jobs, and personnel who configure the integration, whether the fault is human configuration or automated execution.

3. Data quality and shared catalog

The Registry and brand/model catalog are shared across customers. The API Consumer shall not treat the API as a private database. DigiQuip may restrict or suspend write access that breaks catalog discipline or imposes cleanup costs on others.

Catalog rows (brand and model) are created and maintained under DigiQuip product rules, not by arbitrary POST from standard M2M profiles. The API Consumer shall use read endpoints and agreed flows to find existing types before creating assets or asset types.

4. Remediation – billable assistance

The API Consumer acknowledges that faulty or harmful API use may cause DigiQuip and third parties direct and indirect costs, including manual review, recovery, merging, catalog cleanup, support, communication with affected parties, and technical investigation.

DigiQuip may, after written notice or in connection with an incident, perform or procure remediation work required because of the API Consumer’s fault or harmful use. Such work is invoiced to the API Consumer as time and materials at the rates in the main agreement, or at DigiQuip’s standard rates for consulting and data-quality work if not otherwise agreed in writing.

Remediation may include, without limitation:

• Identifying and reversing or correcting incorrect rows
• Merging duplicates and cleaning catalog or asset types
• Recovery from backup where necessary and feasible
• Additional logging, reporting, and documentation to affected parties

Where practicable, DigiQuip will give the API Consumer a preliminary scope estimate before extensive work begins. Urgent remediation to limit harm to other customers may start without prior consent, followed by documentation and invoicing.

5. Indirect costs and third parties

The API Consumer shall indemnify DigiQuip against all claims, losses, expenses, and costs arising from the API Consumer’s faulty or harmful API use, including:

• Direct costs – labour, infrastructure, external consultants engaged by DigiQuip
• Indirect costs – lost productivity, additional support volume, reputational harm to a reasonable documented extent, and administrative costs
• Third-party claims – compensation, refunds, or credits DigiQuip must pay or grant to other customers, end users, tenants, or partners because of incorrect registry data or service disruption caused by the API Consumer’s integration

This clause supplements any indemnity or hold-harmless clause in the main agreement and shall not be read to limit DigiQuip’s rights where the main agreement provides broader protection.

6. Suspension and termination of API access

DigiQuip may suspend or revoke API access without notice if continued use could worsen registry data, security, or other customers’ operations. Where reasonable, DigiQuip will notify the API Consumer and cooperate on a controlled stop of the integration.

Permanent termination of API access follows the main agreement. Remediation costs and indemnity claims that arose before termination remain due.

7. Limitation of liability

Except for remediation and indemnity under sections 4 and 5, and unless mandatory law or the main agreement provides otherwise, limitation of liability and disclaimers agreed between the parties for DigiQuip’s services apply. The API is provided as documented; DigiQuip does not guarantee uninterrupted access beyond any applicable SLA.

8. Audit and logging

DigiQuip may log API calls for security, troubleshooting, and documentation of data-quality incidents. The API Consumer shall, on request, assist with relevant logs and version information from its own systems to explain an incident within a reasonable time.

9. Changes

DigiQuip may update the API Terms by publishing a new version on digiquip.no. Material changes are notified via the channel specified in the main agreement or to the integration contact. Continued API use after the effective date constitutes acceptance unless the main agreement requires express written acceptance.

10. Contact

Questions about API access, scopes, and these terms: support@digiquip.no.

Changelog

Version	Date	Change
1.0	26 October 2026	Initial version – remediation costs and third-party indemnity for API consumers