BDXR service groups

The BDXR SMP variants expose the same URL paths as Peppol SMP but use different XML namespaces and element structures. The active variant is controlled by smp.rest.type = bdxr in application.properties.

Namespace differences

Variant	XML namespace
Peppol SMP 1.x	`http://busdox.org/serviceMetadata/publishing/1.0/`
OASIS BDXR SMP 1.0	`http://docs.oasis-open.org/bdxr/ns/SMP/1/ServiceMetadata`
OASIS BDXR SMP 2.0	`http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceMetadata`

BDXR SMP 2.0 GET requests for service groups and service metadata are served under the /bdxr-smp-2/ path prefix. Write endpoints (PUT, DELETE) use the same paths as Peppol SMP and BDXR 1.0.

GET `/{ServiceGroupId}` — BDXR 1.0

Returns the BDXR 1.0 service group. The path is identical to the Peppol SMP endpoint; the namespace in the XML response differs. Authentication: Not required.

ServiceGroupId

string

required

The participant identifier in scheme::value format, URL-encoded.

Request
Response

curl https://smp.example.org/iso6523-actorid-upis%3A%3A0088%3A5060210000007

<?xml version="1.0" encoding="UTF-8"?>
<ServiceGroup xmlns="http://docs.oasis-open.org/bdxr/ns/SMP/1/ServiceMetadata">
  <ParticipantIdentifier scheme="iso6523-actorid-upis">0088:5060210000007</ParticipantIdentifier>
  <ServiceMetadataReferenceCollection>
    <ServiceMetadataReference
      href="https://smp.example.org/iso6523-actorid-upis%3A%3A0088%3A5060210000007/services/..."/>
  </ServiceMetadataReferenceCollection>
</ServiceGroup>

GET `/bdxr-smp-2/{ServiceGroupId}` — BDXR 2.0

Returns the BDXR 2.0 service group. Uses the /bdxr-smp-2/ path prefix and the BDXR 2.0 namespace. Authentication: Not required.

ServiceGroupId

string

required

The participant identifier in scheme::value format, URL-encoded.

Request
Response

curl https://smp.example.org/bdxr-smp-2/iso6523-actorid-upis%3A%3A0088%3A5060210000007

<?xml version="1.0" encoding="UTF-8"?>
<ServiceGroup xmlns="http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceMetadata">
  <ParticipantID schemeID="iso6523-actorid-upis">0088:5060210000007</ParticipantID>
  <ServiceReference>
    <ID>busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##...</ID>
    <Href>https://smp.example.org/bdxr-smp-2/iso6523-actorid-upis%3A%3A0088%3A5060210000007/services/...</Href>
  </ServiceReference>
</ServiceGroup>

BDXR 2.0 structural differences

BDXR 2.0 renames several elements compared to BDXR 1.0 and Peppol SMP:

Peppol SMP / BDXR 1.0	BDXR 2.0
`ParticipantIdentifier` with `scheme` attribute	`ParticipantID` with `schemeID` attribute
`ServiceMetadataReferenceCollection` / `ServiceMetadataReference`	`ServiceReference` with `ID` and `Href` elements
Signed responses	Unsigned responses

PUT `/{ServiceGroupId}`

Creates or updates a BDXR service group. The request body must use the BDXR 1.0 namespace when smp.rest.type = bdxr is configured. Authentication: Required. See Authentication.

ServiceGroupId

string

required

The participant identifier in scheme::value format, URL-encoded.

BDXR 1.0 request body
BDXR 2.0 request body
curl example

<?xml version="1.0" encoding="UTF-8"?>
<ServiceGroup xmlns="http://docs.oasis-open.org/bdxr/ns/SMP/1/ServiceMetadata">
  <ParticipantIdentifier scheme="iso6523-actorid-upis">0088:5060210000007</ParticipantIdentifier>
  <ServiceMetadataReferenceCollection/>
</ServiceGroup>

<?xml version="1.0" encoding="UTF-8"?>
<ServiceGroup xmlns="http://docs.oasis-open.org/bdxr/ns/SMP/2/ServiceMetadata">
  <ParticipantID schemeID="iso6523-actorid-upis">0088:5060210000007</ParticipantID>
</ServiceGroup>

curl -X PUT \
  https://smp.example.org/iso6523-actorid-upis%3A%3A0088%3A5060210000007 \
  -u [email protected]:password \
  -H "Content-Type: application/xml" \
  --data-binary @bdxr-service-group.xml

Response

Returns HTTP 200 OK with an empty body on success.

Error responses

Status	Condition
`400`	Identifier in URL does not match the identifier in the request body
`401`	Missing or invalid credentials
`403`	Authenticated user does not own the service group

DELETE `/{ServiceGroupId}`

Deletes the BDXR service group and all associated service metadata. This endpoint is the same for BDXR 1.0 and 2.0. Authentication: Required. See Authentication.

ServiceGroupId

string

required

The participant identifier in scheme::value format, URL-encoded.

curl example

curl -X DELETE \
  https://smp.example.org/iso6523-actorid-upis%3A%3A0088%3A5060210000007 \
  -u [email protected]:password

Response

Returns HTTP 200 OK on success.

Error responses

Status	Condition
`400`	Identifier cannot be parsed
`401`	Missing or invalid credentials
`403`	Authenticated user does not own the service group
`404`	No service group with this identifier exists

Overview

Peppol SMP 1.x

OASIS BDXR SMP

Status & Health

BDXR service groups

Namespace differences

GET `/{ServiceGroupId}` — BDXR 1.0

GET `/bdxr-smp-2/{ServiceGroupId}` — BDXR 2.0

BDXR 2.0 structural differences

PUT `/{ServiceGroupId}`

Response

Error responses

DELETE `/{ServiceGroupId}`

Response

Error responses

Build docs developers (and LLMs) love

Overview

Peppol SMP 1.x

OASIS BDXR SMP

Status & Health

​Namespace differences

​GET /{ServiceGroupId} — BDXR 1.0

​GET /bdxr-smp-2/{ServiceGroupId} — BDXR 2.0

​BDXR 2.0 structural differences

​PUT /{ServiceGroupId}

​Response

​Error responses

​DELETE /{ServiceGroupId}

​Response

​Error responses

Build docs developers (and LLMs) love

Namespace differences

GET `/{ServiceGroupId}` — BDXR 1.0

GET `/bdxr-smp-2/{ServiceGroupId}` — BDXR 2.0

BDXR 2.0 structural differences

PUT `/{ServiceGroupId}`

Response

Error responses

DELETE `/{ServiceGroupId}`

Response

Error responses