Authorization

e-conomic
Prerequisites
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.
Step 1: Register as an e-conomic Developer
To obtain an App Secret Token, you must first register a developer agreement on the e-conomic Developer Network.
-
Navigate to https://www.e-conomic.com/developer and click Sign up to create a free developer account.
-
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.
Step 3: Obtain the Agreement Grant Token
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.
Create an e-conomic Credential
- To create a new e-conomic credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Credential Name & Description
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.
API Key Authentication
e-conomic uses a dual-token approach rather than a single API key. Both tokens must be provided to authenticate successfully. 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.
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.
Save the Credential
-
Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.
-
The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.