Developer Terms for e-conomic API
These terms and conditions (the "Terms") constitute a legally binding agreement between Visma e-conomic A/S ("e-conomic") and the legal entity (the "Developer") wishing to use e-conomic's API environments. By creating a developer account or accessing e-conomic's Application, the Developer agrees to be bound by these Terms.
1. Definitions
API: e-conomic's Application Programming Interface, including associated documentation, software development kits (SDKs), protocols, and tools made available by e-conomic to facilitate integration.
Application: The software, service, or integration that the Developer develops using the API.
Application Data: All data generated, processed, or utilized by or through the use of the API or e-conomic's accounting software.
e-conomic: Visma e-conomic A/S, the provider of the API and the accounting software.
Partner/Developer: Any party that accesses, utilizes, or integrates the API with their own systems or services.
Sandbox Environment: A planned test environment available for development, in which no access to actual production data is provided. The environment is established such that data consists solely of synthetic data (dummy data).
Production Environment: The environment where the Developer obtains access to active customer data in e-conomic.
Identification: Verification process where the Developer's legal entity is verified via MitID, BankID, eID, or passport.
Declaration of Purpose: The purpose of the integration declared by the Developer, which constitutes the basis for access.
Usage Limit: A quantifiable limitation on the use of the API (e.g., rate limiting).
Developer Agreement: Means the contract and legal framework governing the Developer’s right of access to the API environment. The scope, restrictions, and conditions of this agreement are determined by the specific representations, declarations, and data submitted by the Developer during the application and onboarding process, as subsequently approved by e-conomic.
Terms: The conditions, obligations, and rights described in this document.
2. Qualification and Registration
2.1 Acceptance: The Partner's acceptance of these Terms is required prior to any access to or use of the API. Partners already using the API are deemed to have accepted the Terms through continued use.
2.2 Corporate Requirements: Production access is only granted to professional entities with a valid CVR number (or equivalent foreign business registration). Private individuals only have access to the Sandbox environment.
2.3 Contact Information: The Developer must provide name, email, address, telephone number, and the expected number of API integrations. It is the Developer's responsibility to ensure that this information is always kept up to date in the developer agreement.
2.4 Identification: Upon requesting production access, the Developer must be verified via MitID, BankID, eID, or passport.
3. Access Levels
3.1 Sandbox Access: Access to the upcoming Sandbox environment will solely be for the purpose of supporting testing and technical validation. Data in this environment will be established without containing personally identifiable information.
3.2 Production Access: Requires formal onboarding, identity approval, and the executed developer agreement (per application). e-conomic may deny access without further justification.
3.3 Monitoring and Compliance: e-conomic continuously monitors the Developer's Applications to ensure that usage and functionality align with the purpose declared by the Developer. e-conomic reserves the right to restrict or suspend access if an Application is deemed not to comply with the declared purpose or the applicable Terms.
4. Product Declaration and Purpose Limitation
4.1 Declaration of Purpose: As part of onboarding, the Developer must submit a detailed "Declaration of Purpose" describing the Application's functionality, data processing, and the precise purpose of the integration.
4.2 Scope of Use: Access to the API is strictly limited to the purpose described in the Declaration of Purpose and approved by e-conomic.
4.3 Local Use: The API may only be used to extend e-conomic's functionality. The Developer may not use the API to develop products that replicate core functionalities of e-conomic (e.g., general ledger or automation) or serve as a replacement for e-conomic.
4.4 User Interface: Applications must offer a unique, value-adding user interface. It is not permitted to use the API as a "headless" backend for a third-party interface that replicates e-conomic's workflow.
4.5 Continuous Updating: The Developer is obliged to continuously ensure that the Product Declaration is updated and reflects the actual use of the API access. e-conomic may at any time request documentation of compliance herewith.
5. Maintenance, Changes, and Deprecation
5.1 Deprecation: e-conomic reserves the right to phase out and close specific endpoints or entire APIs.
5.2 Versioning: In the event of major version changes, the previous version will be supported for a maximum of 12 months. It is the Partner's responsibility to transition to the latest version to avoid service disruptions.
5.3 Maintenance: e-conomic does not provide support for deprecated versions, but reserves the right to perform critical security updates on underlying systems that may affect all versions.
5.4 Changelog: It is the partner's sole responsibility to stay updated on the latest version via the changelog. Continued use constitutes acceptance of these updates.
6. Usage Restrictions
6.1 Installation Limit and Verification: Upon transitioning to the production environment, the Application is assigned an initial quota of 20 installations:
- Notification: When the Application reaches 10 installations, the Developer will receive a notification in order to proactively initiate a manual verification process.
- Soft Block: Upon reaching 20 installations, a restriction ("soft block") is activated unless manual verification has been completed. A soft block implies that new installations of the Application are disabled, while existing installations can continue to be used without changes or restrictions.
- Removal: The restriction is lifted once the Application has been manually verified and approved by e-conomic.
6.2 Developer's Representations
a) By using the API, the Developer agrees to the following usage restrictions:
The Developer's use of the API is subject to the usage restrictions specified in the developer agreement with e-conomic.
Any use of the API that exceeds the restrictions applicable to the Developer requires e-conomic's prior and express consent. e-conomic reserves the right to grant or deny such a request at its sole discretion and may require the Developer's acceptance of additional terms.
e-conomic reserves the right to continuously update or change usage restrictions or fees; however, it will endeavor to provide the Developer with notice of significant changes at least 30 days before the change takes effect.
b) Purpose of Use: The Developer may solely use API data originating from e-conomic's API for the specific purpose of developing, testing, and supporting the functions of the Developer's application in accordance with the Developer's approved use case pursuant to the executed developer agreement, subject to the following restrictions:
1) Training of AI Models: API data must not be used to train, fine-tune, adapt, or optimize any type of AI (artificial intelligence) models.
2) Data Forwarding: API data must not be disclosed to third parties without the prior consent of the relevant user. Under no circumstances may API data be disclosed to third parties for purposes or activities that conflict with these terms.
3) Rate Limiting and Fair Use: Use of the API is regulated via a Token Bucket model. Each endpoint is assigned an individual token cost, which is deducted from the agreement's total token pool upon use. Specifications regarding the size of the pool and the token cost of individual endpoints are managed by e-conomic and can be found in e-conomic's technical API guide.
4) e-conomic reserves the right to introduce tiered token buckets at its sole discretion and without prior notice.
5) Data Storage and Caching Policy: To safeguard system integrity and maintain data consistency, the retrieval and storage of data are subject to the following conditions:
- Prohibition of Secondary Registers: Partners are strictly prohibited from systematically extracting or storing e-conomic data to construct a parallel database or register that functions independently of e-conomic.
- Permitted Caching: Temporary caching of data is allowed exclusively to optimize application performance and minimize unnecessary API load.
- Data Retention: Cached data must not be stored permanently. Instead of performing scheduled, automated bulk updates that put artificial strain on the API, partners must implement dynamic data invalidation that purges or refreshes data based on actual user activity.
7. Right to Restrict Access to the API and e-conomics support
7.1 e-conomic reserves the right to restrict access to the API indefinitely if commercial considerations require it.
7.2 e-conomic is not obligated to provide a justification or notice in connection with such restrictions, particularly during periods of high demand or for reasons of system integrity.
7.3 Developers are responsible for providing direct support to our shared customers, specifically accounting offices (AOs) and business owners (BOs), on all matters related to the use of their integration.
7.4. Developers must not advise AOs or BOs to contact e-conomic support or e-conomic API support for issues arising from the integration. Instead, if an integration-related issue arises, the Developer is required to contact e-conomic’s API support team on behalf of the AO or BO to ensure resolution.
8. Connection to e-conomic Customers
8.1 Developer's Duty of Documentation: In the case of technical integration between a Developer's application and an e-conomic customer, the Developer is responsible for ensuring that the access complies with the Developer's declared purpose.
8.2 Transparency: The Developer must ensure that the customer is always informed about which data is accessed and for what purpose.
8.3 Consent: The Developer must never access customer data without explicit consent from the authorized signatory or an authorized administrator of the customer.
9. Financial Terms and Indemnification
9.1 Free Access: e-conomic does not charge fees for access to the API development environment.
9.2 Fair Use: e-conomic reserves the right to introduce restrictions (rate limiting) to ensure the stability of the platform.
9.3 Change of Price Model: e-conomic reserves the right to introduce fees for API access or specific service levels in the future with 60 days' notice.
9.4 Indemnification: The Developer shall indemnify and hold e-conomic harmless from any claim, loss, or cost (including legal fees) arising as a result of the Developer's use, misuse of the API, or negligence in accordance with the general law of damages under Danish law.
9.5 Security Breach: The Partner must immediately inform e-conomic via api@e-conomic.com of any security breach related to the use of the API.
10. Misuse of Access to the Application
A. The Developer must under no circumstances (non-exhaustive):
- Use the API for purposes other than the purpose declared in the developer agreement.
- Attempt to bypass security measures or unreasonably burden the infrastructure.
- Extract data with the aim of creating a competing product (reverse engineering).
- Use data from the API for training AI models without a separate written agreement.
B. In the event of any violation of the above or similar misuse, e-conomic reserves the right to claim damages from the Developer in question. Unless the financial loss can be calculated to an amount greater than DKK 100,000, any violation will always amount to DKK 100,000 per violation, and DKK 10,000 per 24-hour period until the breach has finally ceased.
C. Any violation of litra A will, without further notice, result in a termination of the developer agreement.
11. Disclaimer of Warranties
11.1 "As Is" Delivery: The API and associated services are provided "as is" without any kind of warranty regarding response time, uptime, accuracy, or fitness for specific purposes.
11.2 Changes: e-conomic may at any time and without notice change the API specifications, which may require updates to the Developer's Application at their own risk and expense.
12. Limitation of Liability
12.1 Indirect Losses: e-conomic is under no circumstances liable to the Developer or any third party for indirect losses, including loss of business, loss of data, loss of revenue, or goodwill.
12.2 Maximum Liability: As access to the API is free of charge, e-conomic's total liability for any loss arising out of or in connection with these Terms is limited to DKK 0.
12.3 Force Majeure: e-conomic is not liable for non-performance resulting from circumstances beyond e-conomic's reasonable control.
13. Breach and Termination
13.1 Suspension: e-conomic may immediately suspend access to the API if suspicion of misuse, security breach, or violation of the Product Declaration arises.
13.2 Termination: Both parties may terminate the agreement with 30 days' notice. In the event of a breach or suspicion thereof, e-conomic may terminate the agreement without notice.
14. Application Data
14.1 e-conomic may use Application Data to maintain, offer, price, and develop the e-conomic application.
14.2 Data may be shared with other companies within the Visma Group in accordance with the Data Processing Agreement.
14.3 Upon termination, e-conomic is entitled to process Application Data in an anonymized form. Government/Authority access is only granted in accordance with legislation or court orders.
15. Governing Law and Jurisdiction
Any dispute that may arise from these Terms shall be settled in accordance with Danish law by the Maritime and Commercial Court (Sø- og Handelsretten).
Updated the 12/06/2026
Need help?
We are ready to help you with your API questions at api@e-conomic.com.
And if you have questions regarding apps, don't hesitate to contact apps@e-conomic.com.