Skip to main content

Authorization

Follow this guide to create a new Invoiced credential that will allow Nexla to authenticate to and exchange data with your Invoiced account.
invoiced_api_auth.png

Invoiced

Prerequisites​

To connect Nexla to Invoiced, you need an active Invoiced account and an API key. Invoiced uses HTTP Basic Authentication, where your API key serves as the username for all API requests.

Create an Invoiced API Key​

Invoiced uses API key-based authentication. Each business account on Invoiced maintains its own set of API keys, and it is recommended to create a dedicated API key for each application or integration that will make API calls on your behalf. This allows you to revoke access for a specific integration without affecting others.

  1. Sign in to your Invoiced account at invoiced.com.

  2. Click on your account name or avatar in the upper-right corner to open the account menu, and select Settings.

  3. In the left navigation panel, click Developers.

  4. Under the Developers section, click API Keys.

  5. Click the New API Key button (or Generate API Key) to create a new key.

  6. Enter a descriptive label for the key (for example, "Nexla Integration") to help identify its purpose later, and click Save or Create.

  7. Copy the generated API key immediately and store it in a secure location. The key value is displayed only once and cannot be retrieved again after you navigate away from the page.

Invoiced also provides a sandbox environment for testing at sandbox.invoiced.com. You can create a separate API key in the sandbox environment using the same steps above. Use sandbox credentials with Nexla when testing your integration before going live. The sandbox API base URL is https://api.sandbox.invoiced.com, while the production URL is https://api.invoiced.com.

For complete information about the Invoiced API and authentication, visit the Invoiced Developer Documentation.

Create an Invoiced Credential​

  • To create a new Invoiced credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. 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​

Invoiced authenticates API requests using HTTP Basic Authentication, where your API key is passed as the username and the password field is left empty. Nexla handles this encoding automatically when you enter your API key.

  1. Enter your Invoiced API key in the API Key field. This is the key you generated in the Invoiced dashboard under Settings > Developers > API Keys. The key authenticates all API requests Nexla makes on behalf of your Invoiced account.

    Important

    Keep your API key confidential. Anyone with your API key can access your Invoiced data with the same permissions as your account. Avoid sharing API keys or committing them to source code repositories. If a key is compromised, revoke it immediately from the Invoiced dashboard and generate a new one.

  2. If you are connecting to the Invoiced sandbox environment for testing rather than the production environment, enter the sandbox base URL (https://api.sandbox.invoiced.com) in the Base URL field. For production use, enter https://api.invoiced.com.

    The sandbox environment is a safe, isolated space for testing your Nexla integration without affecting your live billing data. Invoiced sandbox accounts are separate from production accounts and require their own API keys.

Save the Credential​

  1. 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.

  2. 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.