Skip to content
2026-08-05
PeppolNews
Briefed on Peppol.
The Weekly Brief Search
PN-20260625 vendors
Vendors

Denmark's NHR API gets breaking changes on August 12, 2026

Denmark's NHR lookup API is changing field names from camelCase to PascalCase on August 12, 2026. Integrations must update JSON parsing for `profile` and `role` objects. Demo environment is live now.

Nemhandel has released a new version of Denmark’s NHR API with breaking changes that take effect August 12, 2026. Field names in profile and role objects are shifting to PascalCase, and two boolean flags are being renamed. Integrations must update their JSON parsing before the production deadline.

Nemhandel, the Danish e-invoicing authority, has announced breaking changes to the NHR API (lookup API) effective August 12, 2026. The demo environment is available now for testing.

Breaking changes requiring code updates

Two sets of field names are changing from camelCase to PascalCase:

In the profile object:

  • id becomes Id
  • name becomes Name
  • description becomes Description
  • profileId becomes ProfileId
  • profileGroup becomes ProfileGroup
  • profileGroupId becomes ProfileGroupId
  • nemhandelAs4Enabled becomes IsNhAs4Enabled
  • peppolEnabled becomes IsPeppolEnabled

Note: The old version contained both peppolEnabled and IsPeppolEnabled. Going forward, only IsPeppolEnabled will exist.

In the role object:

  • id becomes Id
  • name becomes Name
  • roleId becomes RoleId

Integrations must update their JSON parsing for both objects. This is the only change requiring code modifications.

New optional fields

Three new additions are available but not required:

  • ActiveInDkSml and ActiveInEuSml on the participant object. These boolean fields show whether a participant is registered in the Danish SML and EU SML respectively.
  • CertificateBindings on receiver services. This new list allows scheduling certificate changes by setting activation and expiration dates. Each binding includes Id, CertificateId, ReceiverServiceId, ActivationDate, ExpirationDate, and lastModifiedString.
  • DocumentStandardId and NetworkTypeId on the profile object.

Timestamp field change

The last-modified timestamp is now provided in the field lastModifiedString. Nemhandel recommends that integrations use this field going forward.

Timeline and next steps

The demo environment is live at api-demo.nemhandel.dk. Production deployment occurs on August 12, 2026.

Integrations should:

  1. Update JSON parsing for profile and role objects to use PascalCase field names.
  2. Switch from peppolEnabled/nemhandelAs4Enabled to IsPeppolEnabled/IsNhAs4Enabled.
  3. Use lastModifiedString for the last-modified timestamp.
  4. Test against the demo environment and verify integration before production.
  5. Optionally adopt the new fields if relevant to your use case.

For questions, contact Nemhandel Support at support@nemhandel.dk.

References

  1. Nemhandel, Nyheder og releases (DK)