e-conomic, by Visma, is a leading cloud-based accounting and ERP platform for small and medium businesses, used by 260,000+ companies across Denmark and the Nordics. It simplifies financial management with invoicing, expense tracking, bank reconciliation, journal bookkeeping, and reporting. Its open REST API and app marketplace enable seamless integration to synchronise financial data across systems.
Power end-to-end data operations for your e-conomic API with Nexla. Our bi-directional e-conomic connector is purpose-built for e-conomic, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to e-conomic or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your e-conomic workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The e-conomic REST API uses a dual-token authentication model. Every API request must include two tokens sent as request headers: an App Secret Token that identifies your integration, and an Agreement Grant Token that authorises the integration to access a specific e-conomic agreement (company account). Both tokens are required — neither alone is sufficient to authenticate.
Complete the registration form. After registering, e-conomic will send an email with login credentials for your new developer agreement.
Sign in to your developer agreement using the credentials provided in the welcome email.
Step 2: Register an App and Obtain the App Secret Token
The App Secret Token (X-AppSecretToken) identifies your specific integration. You create this once by registering an app in the developer portal.
After signing in to your developer agreement, navigate to the Apps section of the developer portal.
Click Create App (or Register App) and provide a name and description for your integration.
Once the app is created, the portal will display your App Secret Token. Copy this token and store it securely — it will be needed when configuring the Nexla credential.
The App Secret Token is a long-lived credential that identifies your integration. Treat it as a secret and do not share it publicly. If the token is compromised, regenerate it from the developer portal.
The Agreement Grant Token (X-AgreementGrantToken) grants your app access to a specific e-conomic company agreement. This token is generated by the e-conomic account holder who is authorising the integration.
Sign in to the e-conomic account for the company whose data you want to access.
Navigate to Settings > Integrations (or use the Tokens section of the developer portal, available after signing in to your developer agreement).
Click the Tokens button or option to generate a new token for your registered app.
Provide the redirect URL when prompted (a placeholder URL can be used for testing purposes). After the authorisation is accepted, e-conomic provides the Agreement Grant Token as a URL parameter in the redirect response.
Copy the Agreement Grant Token from the redirect URL and store it securely.
Each e-conomic agreement (company) requires its own Agreement Grant Token. If you need to connect Nexla to multiple e-conomic company accounts, a separate token must be obtained for each account. For additional details, see the e-conomic developer authentication guide.
e-conomic REST API dual-token authentication. Requires both X-AppSecretToken (developer/app credential) and X-AgreementGrantToken (per-agreement user credential) headers on every request.
Field
Required
Secret
Description
App Secret Token
Yes
Yes
X-AppSecretToken - the developer/app credential issued by e-conomic when registering an app. Identifies the integration.
Agreement Grant Token
Yes
Yes
X-AgreementGrantToken - the per-agreement user credential obtained after the customer grants the app access to their e-conomic agreement.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
e-conomic uses a dual-token approach rather than a single API key. Every request Nexla makes to the e-conomic REST API will include these tokens as X-AppSecretToken and X-AgreementGrantToken headers. Enter your App Secret Token in the App Secret Token field. This is the token that identifies your integration, obtained when registering your app in the e-conomic developer portal.
Enter your Agreement Grant Token in the Agreement Grant Token field. This is the per-agreement token that grants access to a specific e-conomic company account.
Important
Both tokens are transmitted securely and stored encrypted by Nexla. Do not share these tokens with unauthorised parties. If either token is compromised, revoke and regenerate it from the e-conomic developer portal before updating your Nexla credential.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the e-conomic connector tile, then select the credential that will be used to connect to the e-conomic account, and click Next; or, create a new e-conomic credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common e-conomic endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List Accounts
Returns the complete list of accounts defined in the e-conomic chart of accounts for your agreement. Use this endpoint to export your account structure for reporting, reconciliation, or synchronisation with an external system.
No additional parameters are required. Select the List Accounts template and Nexla will automatically call the GET /accounts endpoint and paginate through all available accounts.
The endpoint returns one account record per item in the response collection. Each record includes the account number, account name, account type, balance, and related metadata.
Returns the complete list of customers registered in your e-conomic account. Use this endpoint to export customer master data for CRM synchronisation, analytics, or external reporting.
No additional parameters are required. Select the List Customers template and Nexla will automatically paginate through all customer records using the GET /customers endpoint.
Each record includes customer number, name, address, VAT zone, currency, payment terms, and links to related resources such as contacts and invoices.
Returns the list of journals defined in your e-conomic agreement. Journals in e-conomic are bookkeeping registers used to post vouchers and accounting transactions. Use this endpoint to retrieve journal definitions for reference when creating journal vouchers or auditing your accounting structure.
No additional parameters are required. Select the List Journals template and Nexla will automatically call the GET /journals endpoint and paginate through all available journals.
Each record includes the journal number, name, voucher number range settings, and convenience links to voucher and entry collections.
Returns all products available in the e-conomic product catalogue for your agreement. Use this endpoint to export product data for inventory management, pricing analysis, or synchronisation with an e-commerce or ERP system.
No additional parameters are required. Select the List Products template and Nexla will automatically paginate through all product records using the GET /products endpoint.
Each record includes the product number, name, sales price, cost price, unit of measure, and stock information where applicable.
List Draft Invoices
Retrieves all draft invoices in your e-conomic account. Draft invoices are work-in-progress invoices that have not yet been booked and are not legally binding. Use this endpoint to monitor invoices awaiting review or approval before they are finalised.
No additional parameters are required. Select the List Draft Invoices template and Nexla will automatically paginate through all draft invoices using the GET /invoices/drafts endpoint.
Each record includes invoice number, customer reference, invoice lines, amounts, currency, due date, and current status within the drafting workflow.
List Booked Invoices
Retrieves all booked (finalised) invoices in your e-conomic account. Booked invoices have been formally recorded in the accounting system and are legally binding documents. Use this endpoint to export completed invoice records for revenue analysis, accounts-receivable reporting, or data warehousing.
No additional parameters are required. Select the List Booked Invoices template and Nexla will automatically paginate through all booked invoices using the GET /invoices/booked endpoint.
Each record includes booked invoice number, date, customer details, line items, gross and net amounts, VAT amounts, and payment status.
List Paid Invoices
Retrieves all invoices that have been fully paid in your e-conomic account. Use this endpoint to track completed payment activity and generate cash-flow or accounts-receivable reports.
No additional parameters are required. Select the List Paid Invoices template and Nexla will automatically paginate through all paid invoices using the GET /invoices/paid endpoint.
Each record includes booked invoice details along with the recorded payment date and amount.
List Overdue Invoices
Retrieves all invoices that have passed their due date without full payment. Use this endpoint to monitor outstanding debt, prioritise collections activity, or trigger automated follow-up workflows in Nexla.
No additional parameters are required. Select the List Overdue Invoices template and Nexla will automatically paginate through all overdue invoices using the GET /invoices/overdue endpoint.
Each record includes the invoice details, due date, and outstanding balance, enabling downstream alerts or debt-collection workflows.
List Unpaid Invoices
Retrieves all booked invoices that have not yet been fully paid, regardless of whether they are overdue. This is a broader set than overdue invoices and is useful for accounts-receivable reporting and cash-flow forecasting.
No additional parameters are required. Select the List Unpaid Invoices template and Nexla will automatically paginate through all unpaid invoices using the GET /invoices/unpaid endpoint.
Each record includes invoice details, outstanding balance, due date, and payment status information.
List Not Due Invoices
Retrieves all booked invoices that are not yet past their due date. Use this endpoint to plan upcoming payment expectations and forecast short-term cash inflows.
No additional parameters are required. Select the List Not Due Invoices template and Nexla will automatically paginate through all not-due invoices using the GET /invoices/not-due endpoint.
Each record includes invoice details, due date, and outstanding balance.
Get Invoice Totals
Retrieves summary totals aggregated across all invoices in the account. Use this endpoint for high-level financial dashboards that display total invoiced amounts, total outstanding balances, and aggregate payment status.
No additional parameters are required. Select the Get Invoice Totals template and Nexla will call the GET /invoices/totals endpoint and return the summary object as a single record.
The response is a single JSON object (not a paginated list) containing aggregate amounts grouped by invoice status (paid, unpaid, overdue, not due).
Because this endpoint returns a summary object rather than a collection, Nexla is configured to treat the entire response as a single record. This endpoint is well-suited for use in scheduled dashboard refresh flows.
List Sent Invoices
Retrieves all invoices that have been sent to customers. Use this endpoint to track invoice delivery activity and confirm which customers have been billed.
No additional parameters are required. Select the List Sent Invoices template and Nexla will automatically paginate through all sent invoices using the GET /invoices/sent endpoint.
Each record includes invoice details along with delivery metadata such as the date and method by which the invoice was sent.
List Draft Orders
Returns all draft orders in the e-conomic system. Draft orders are sales orders that are still being prepared and have not yet been sent to customers. Use this endpoint to monitor orders in progress or synchronise order pipeline data with an external system.
No additional parameters are required. Select the List Draft Orders template and Nexla will automatically paginate through all draft orders using the GET /orders/drafts endpoint.
Each record includes order number, customer reference, order lines, amounts, and current order status.
List Sent Orders
Returns all sent orders in the e-conomic system. Sent orders have been transmitted to customers but may not yet have been converted into invoices. Use this endpoint to track order fulfilment status and reconcile order data with shipping or ERP systems.
No additional parameters are required. Select the List Sent Orders template and Nexla will automatically paginate through all sent orders using the GET /orders/sent endpoint.
Each record includes order details along with the date the order was sent.
List Archived Orders
Returns all archived orders in the e-conomic system. Archived orders are historical orders that have been closed or converted, providing a complete record of past sales order activity. Use this endpoint for historical reporting or data archiving workflows.
No additional parameters are required. Select the List Archived Orders template and Nexla will automatically paginate through all archived orders using the GET /orders/archived endpoint.
Each record includes the full order details captured at the time of archiving.
List Booked Entries
Returns the immutable list of all booked (posted) general-ledger entries in your e-conomic account. Booked entries form the permanent audit trail produced when invoices and journal vouchers are posted. Use this endpoint for accounting reconciliation, audit reporting, or feeding a data warehouse with the full general-ledger history.
No additional parameters are required. Select the List Booked Entries template and Nexla will automatically paginate through all booked general-ledger entries using the GET /entries/booked endpoint.
Each record includes entry number, account number and name, voucher number, amount (debit/credit), booking date, and the journal from which the entry originated.
Booked entries are immutable — once created, they cannot be modified or deleted. This endpoint is therefore an authoritative source for audit and compliance reporting. Additional reference information is available in the e-conomic Booked Entries API documentation.
List Subscriptions
Returns all subscriptions (recurring billing plans) configured in the e-conomic account. Use this endpoint to track recurring revenue, monitor subscription lifecycle, or synchronise subscription data with a SaaS billing or CRM platform.
No additional parameters are required. Select the List Subscriptions template and Nexla will automatically paginate through all subscription records using the GET /subscriptions endpoint.
Each record includes subscription details such as billing interval, associated customer, and subscription status.
List Dimensions
Returns all dimension and cost-centre definitions used in your e-conomic account. Dimensions allow organisations to tag accounting transactions with departmental, project, or cost-centre codes, enabling more granular financial analysis. Use this endpoint to export dimension definitions for use in reporting or to enrich general-ledger data with cost-centre context.
No additional parameters are required. Select the List Dimensions template and Nexla will automatically paginate through all dimension records using the GET /dimensions endpoint.
Each record includes the dimension number, name, and any associated member values.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
e-conomic data sources can also be manually configured to ingest data from any valid e-conomic REST API endpoint not covered by the pre-built templates, using custom filters, query parameters, or chained API calls. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The e-conomic REST API base URL is https://restapi.e-conomic.com; full reference documentation is available at https://restdocs.e-conomic.com. e-conomic list responses wrap results in a collection array, so the path to data for most list endpoints is $.collection[*] — for summary endpoints that return a single object (such as GET /invoices/totals), use $ instead. The e-conomic API uses yyyy-MM-dd date format. You do not need to include the X-AppSecretToken or X-AgreementGrantToken authentication headers manually — these are automatically injected by Nexla from the selected e-conomic credential.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new e-conomic data source. Nexla will now begin ingesting data from the configured endpoint and will organise any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the e-conomic destination, and select the Send to Destination option from the menu. Select the e-conomic connector from the list of available destination connectors, then select the credential that will be used to connect to the e-conomic account, and click Next; or, create a new e-conomic credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common e-conomic endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create Customer
Creates a new customer record in the e-conomic system. Use this endpoint to push customer data from an external CRM, e-commerce platform, or onboarding system into e-conomic as part of an automated customer creation workflow.
No additional URL parameters are required for this endpoint. Select the Create Customer template and ensure that the Nexset being sent contains the required customer fields.
At minimum, the request body must include the following fields as required by the e-conomic API:
name — The customer's full name or company name.
currency — A reference object containing the ISO 4217 currency code (e.g., {'code': 'DKK'}).
paymentTerms — A reference object containing the payment terms number.
customerGroup — A reference object containing the customer group number.
vatZone — A reference object containing the VAT zone number.
Optional fields such as address, city, zip, country, email, phone, and corporateIdentificationNumber can also be included in the Nexset payload.
Nexla sends each Nexset record as a separate JSON POST request to the e-conomic Customers API. For full details on available request body fields, see the e-conomic Customers API documentation.
Update Customer
Updates an existing customer record identified by the customer's unique number. Use this endpoint to synchronise customer changes from an external system (such as a CRM or ERP) back into e-conomic, keeping customer master data consistent across platforms.
This endpoint requires one additional parameter:
Customer Number — Enter the unique e-conomic customer number of the customer to be updated. This value is used to construct the API URL (PUT /customers/{customerNumber}) and must correspond to an existing customer in your e-conomic account.
The request body should include all customer fields that need to be updated. The e-conomic API uses a full replacement (PUT) approach, so all required fields must be present in the payload even if they are not being changed.
Required fields are the same as for the Create Customer endpoint: name, currency, paymentTerms, customerGroup, and vatZone.
The Customer Number is the unique numeric identifier assigned by e-conomic when the customer is created. It can be retrieved using the e-conomic List Customers data source or found in the e-conomic user interface under the customer record.
Create Draft Invoice
Creates a new draft invoice in the e-conomic system. Draft invoices are the primary entry point for the e-conomic invoicing lifecycle — they must be created before they can be reviewed, edited, and ultimately booked (finalised) as legally binding invoices. Use this endpoint to automate invoice creation from order management systems, billing platforms, or project management tools.
No additional URL parameters are required. Select the Create Draft Invoice template and ensure that the Nexset contains the required invoice fields.
At minimum, the request body must include:
date — The invoice date in yyyy-MM-dd format.
currency — A reference object containing the ISO 4217 currency code.
paymentTerms — A reference object containing the payment terms number.
customer — A reference object containing the customer number.
recipient — An object containing the recipient name and VAT zone.
lines — An array of invoice line objects, each containing product, quantity, unit price, and VAT account details.
A draft invoice can be reviewed and edited within e-conomic before being booked. To programmatically book the draft and convert it to a legally binding invoice, use the Book Invoice endpoint after the draft is created. Full field documentation is available in the e-conomic Draft Invoices API documentation.
Book Invoice
Books (finalises) a draft invoice by converting it into a legally binding booked invoice. Once booked, the invoice is permanently recorded in the e-conomic accounting system and generates an immutable general-ledger entry. Use this endpoint as the final step in an automated invoice creation workflow, after verifying that the draft invoice is correct.
No additional URL parameters are required. Select the Book Invoice template and ensure the Nexset contains a reference to the draft invoice to be booked.
The request body must include a reference to the draft invoice:
draftInvoice — An object containing the draft invoice number to be booked (e.g., {'draftInvoiceNumber': 123}).
Booking an invoice is irreversible — once booked, the invoice cannot be deleted or edited within e-conomic. Ensure that the draft invoice has been reviewed and approved before triggering this endpoint. For full field documentation, see the e-conomic Booked Invoices API documentation.
Create Draft Order
Creates a new draft order in the e-conomic system. Draft orders represent sales orders in preparation that have not yet been sent to customers. Use this endpoint to push order data from an external e-commerce or ERP system into e-conomic for fulfilment and invoicing.
No additional URL parameters are required. Select the Create Draft Order template and ensure the Nexset contains the required order fields.
At minimum, the request body should include:
date — The order date in yyyy-MM-dd format.
currency — A reference object containing the ISO 4217 currency code.
paymentTerms — A reference object containing the payment terms number.
customer — A reference object containing the customer number.
recipient — An object containing the recipient name and VAT zone.
lines — An array of order line objects containing product, quantity, and unit price details.
Updates an existing draft order identified by the order number, before it has been sent. Use this endpoint to synchronise order changes from an external system back into e-conomic — for example, updating quantities, delivery dates, or line items on pending orders.
This endpoint requires one additional parameter:
Draft Order Number — Enter the unique e-conomic draft order number of the order to be updated. This value is used to construct the API URL (PUT /orders/drafts/{orderNumber}) and must correspond to an existing draft order in your e-conomic account.
The request body should include all order fields using the same structure as Create Draft Order. Because the e-conomic API uses a full replacement (PUT) approach, all required fields must be present in the payload.
The Draft Order Number can be retrieved using the e-conomic List Draft Orders data source or found within the e-conomic user interface under the relevant order record.
Create Draft Quote
Creates a new draft quote (quotation) in the e-conomic system. Quotes allow you to send pricing proposals to customers before a formal order or invoice is raised. Use this endpoint to automate quote generation from a CRM, CPQ, or sales management platform.
No additional URL parameters are required. Select the Create Draft Quote template and ensure the Nexset contains the required quote fields.
The request body structure is similar to draft orders and invoices, and should include at minimum:
date — The quote date in yyyy-MM-dd format.
currency — A reference object containing the ISO 4217 currency code.
paymentTerms — A reference object containing the payment terms number.
customer — A reference object containing the customer number.
recipient — An object containing the recipient name and VAT zone.
lines — An array of quote line objects containing product, quantity, and unit price details.
Creates a new product in the e-conomic product catalogue. Use this endpoint to synchronise product or service catalogue data from an external PIM, e-commerce platform, or ERP system into e-conomic, ensuring that product definitions are consistent across systems.
No additional URL parameters are required. Select the Create Product template and ensure the Nexset contains the required product fields.
At minimum, the request body must include:
productNumber — A unique identifier string for the product.
name — The product name or description.
salesPrice — The default sales price for the product.
productGroup — A reference object containing the product group number.
Optional fields include costPrice, recommendedPrice, unit, description, and stock-related fields.
Updates an existing product in the e-conomic product catalogue, identified by the product number. Use this endpoint to push price changes, description updates, or stock information from an external system back into e-conomic.
This endpoint requires one additional parameter:
Product Number — Enter the unique e-conomic product number of the product to be updated. This value is used to construct the API URL (PUT /products/{productNumber}) and must correspond to an existing product in your e-conomic account.
The request body should include all product fields using the same structure as Create Product. Because the e-conomic API uses a full replacement (PUT) approach, all required fields must be present.
Product numbers can be retrieved using the e-conomic List Products data source or found within the e-conomic product catalogue in the user interface.
Create Supplier
Creates a new supplier record in the e-conomic system. Use this endpoint to import supplier master data from an external procurement, ERP, or vendor management platform into e-conomic, ensuring that supplier records are consistent across all systems.
No additional URL parameters are required. Select the Create Supplier template and ensure the Nexset contains the required supplier fields.
At minimum, the request body must include:
name — The supplier's full name or company name.
currency — A reference object containing the ISO 4217 currency code.
paymentTerms — A reference object containing the payment terms number.
supplierGroup — A reference object containing the supplier group number.
vatZone — A reference object containing the VAT zone number.
Optional fields include address, city, zip, country, email, phone, and corporateIdentificationNumber.
Creates a journal voucher (bookkeeping entry) in a specified e-conomic journal. Journal vouchers are used to post accounting transactions such as expenses, payroll, bank imports, and other general-ledger entries. Use this endpoint to automate the creation of accounting transactions from external payroll, expense management, or banking systems.
This endpoint requires one additional parameter:
Journal Number — Enter the unique number of the e-conomic journal in which the voucher will be created. This value is used to construct the API URL (POST /journals/{journalNumber}/vouchers). The Journal Number can be retrieved using the e-conomic List Journals data source.
The request body must include the voucher details:
accountVoucher — An array of voucher line objects, each specifying an account number, amount, text description, and date.
date — The voucher date in yyyy-MM-dd format.
Journal vouchers must be associated with an existing journal in your e-conomic account. The Journal Number must correspond to a journal that is open for new entries. For full field documentation, see the e-conomic Journals API documentation.
e-conomic destinations can also be manually configured to send data to any valid e-conomic REST API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The e-conomic REST API base URL is https://restapi.e-conomic.com, and requests must be sent in JSON format. For update operations (PUT), include the unique identifier of the resource at the end of the URL path — for example, https://restapi.e-conomic.com/customers/42 to update customer number 42. You do not need to include the X-AppSecretToken or X-AgreementGrantToken authentication headers manually — these are automatically injected by Nexla from the selected e-conomic credential. Most e-conomic write endpoints accept a single JSON object per request rather than arrays, so record batching is best suited to custom or bulk-capable endpoints.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the e-conomic account, open the destination resource menu and select Activate.
The Nexset data will not be sent to e-conomic until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over when data movement begins.
