Changelog
Privacy Policy -->



Version 2.3.0

2025-10-27

Important note: the behaviour or Auto-publish (‘publish_in_smp’) for organizations has changed! See below.

Change summary:

  • Organizations have a new field ‘reference’
  • The managed connection with ion-SMP has been extended and is now more flexible
  • If you are the administrator of an account, you can now request discount bundle changes through the API and the web interface.
  • A few API features have been added for managing organizations, such as a single endpoint to create an organization with identifiers and receive triggers

Reference field for organizations

Organizations have an optional field ‘reference’, which can be used to group organizations. You can use any string value for this field. If set for one or more organizations, it will also be used in transaction count reports, where the organizations will have their reference prepended, and each unique reference will get its own tally. On the organizations view, you can filter by reference.

In the API, this has the following changes:

  • organization endpoints have a new optional string field reference
  • the organizations/ endpoint has a new filter filter_reference, which does a case insensitive partial match comparison

ion-SMP integration

You can specify, per organization identifier, whether to publish the identifier as a receiver in ion-SMP, and specify whether this identifier is capable of receiving any of the following document types:

  • Peppol BIS 3 invoice and creditnote
  • SI-UBL 2 (NLCIUS) invoice and creditnote
  • Invoice Response

If no options are selected, the identifier is not published as a receiver.

Leave these options disabled if your receiving capabilities are managed by a different SMP, or if you manage them yourself.

The organization-level setting ‘publish_in_smp’ (also known as Auto-publish) has been changed; it no longer directly controls the identifier publications, but only enables the above flags when creating new identifiers. Existing identifiers, and whether they are published, are not affected by changing the organization-level value.

This results in the following specific changes in the API:

  • Added 3 boolean fields to the organization identifier endpoints:
    1. publish_receive_peppolbis
    2. publish_receive_nlcius
    3. publish_receive_invoice_response

These have been added to the web-interface as checkboxes as well.

Identifiers are automatically published if any of these are set. The update/creation fails if they cannot be published. When all are unset, the publication is removed.

Note: the options for publishing in ion-SMP are only a small subset of the full features that ion-SMP supports, in order to keep this API simple. Should you require more extensive options for managing your SMP publications, you can register for a separate account on ion-SMP.

Requesting transaction discount bundle changes

On the Account page, if you are an account administrator, you will now find a new card ‘Transaction Bundle’. You can update your account’s transaction bundle here. If you request this change before the 16th of the month, it will be effective as of next month. If you request it later, it will be effective for the month after next.

You can also do this through the new API endpoint at api/v2/account/transaction-bundle

Additional API features

  • When retrieving Organizations data through the API, the data object now also includes the organizations’ identifier(s). These are read-only; you still need to update them through the standard identifiers endpoint(s), but this does mean the organizations list also provides an overview of active peppol identifiers.
  • An additional API endpoint has been added to create organizations: /organizations/create-full; here you can directly provide the organization data, including identifiers and receive triggers. This way, you can create an organization and its configuration in a single instruction. Note that you can still use the standard CRUD endpoints as well. Also note that you cannot add other organization information (such as users) this way, only receive_triggers and identifiers.

Version 2.2.0

API:

  • added a number of endpoints for recipient capability discovery (e.g. lookups): Check Participant Presence, Discover Participant Document Types, Discover Participant Endpoints, and Discover Participant Endpoints for Document. See https://production.ion-ap.net/api_docs/v2/redoc/#tag/discover for a full description.

Version 2.1.0

General:

  • The internal capability discovery system has been overhauled to make better use of caching. When sending a document, a quick existence check for the recipient is executed, rather than just queueing the message whether or not the recipient exists.
  • The ‘publish in SMP’ option has been simplified and enabled: you can now configure organizations to automatically be published in the SMP, with default mandatory document types.

Web interface:

  • The web interface has been overhauled to provide a cleaner UI and prepare for future additions.
  • You can now filter on several properties of transactions, as well as on organization names if their account is for multiple organizations.
  • There is a manual ‘mark read/unread’ button for received documents.
  • You can now convert sent and received invoice documents to PDF. Note that this conversion only renders the main information and may not show complicated documents completely. This feature is considered experimental.

API changes:

  • added several filter options for sent and receive transaction endpoints. These have been added as separate query parameters (rather than a general search option) for use-case flexibility. Multiple parameters will be treated using logical ‘and’.
  • added ‘filter_name’ query parameter to organization list endpoint
  • added a new field to receive_triggers: enabled (boolean). If this field is set to false, the trigger will not run. This is intended to (temporarily) disable the trigger.
  • the user_data api call now shows the account type too
  • added two new action endpoints to receive-transactions: /mark_read and /mark_unread, to directly change the ‘state’ from ’new’ to ‘read’ and vice-versa
  • added the optional-per-organization ‘publish in smp’ option: when enabled, all of the organization’s identifiers will automatically be published with default document types for the organization.
  • removed the endpoints for receivable document types, which were already marked as ’not implemented’. We will look into adding functional ones during the next major version, but for now, the SMP connection only supports default document types.

Version 2.0.0

Initial public release of ion-AP 2.0.