1. Business Registry Configuration
  2. API Configuration

Business Registry Configuration

The Business Registry Configuration is used to configure the data of your own company or your customer's company. It is the entity that represents a company managed by your account, where you can manage configurations such as:

  • enabling the supplier invoice receiving
  • enabling the legal storage
  • enabling the signature
  • manage the webhooks (see Api Configuration)

You can manage these resources via REST API or using the dashboard in the "Business Registry" section.

API Configuration

The API Configuration is the entity that represents the configuration of your webhooks, where you can manage the endpoints that will be called when a specific event occurs. You can manage these resources via REST API or using the dashboard in the "Integrations" section.

The main parts of the API Configuration are:

  • event: the event that triggers the call to your endpoint
  • target_url: the endpoint that will be called

More details about the events and the payload sent to your endpoint can be found in the Webhooks section.

The API Configuration entity can be linked to a Business Registry Configuration or not.

  • If is not linked: the webhook will be called for the event specified for all the companies managed by your account. For example, if you set up a webhook for the supplier-invoice event, it will called when an invoice is received from SDI related to any company managed by your account.
  • On the other hand, if it is linked to a specific Business Registry Configuration, the endpoint will be called only for the events related to that company. For example, if you have have a Business Registry Configuration for a company X and you add a Api Configuration for the supplier-invoice event linked to the company X, the endpoint will be called only when an invoice is received from SDI where the recipient is the company X.


You can decide how to validate the caller in two ways:

  1. The A-CUBE API Platform uses the HTTP Signature to sign the requests sent to your endpoint. You can validate the signature using the public key we provide.
  2. Alternatively, you can manage authentication parameters independently (see API Configuration. We add these parameters to the request sent to your servers based on configurations.