Audience · developers
API, mapping and integrations without dead ends
For technical teams that need more than a browser upload: stable interfaces, batch processing, event contracts, mapping and a clear boundary between preparation tooling and certified PEPPOL delivery.
Developer entry points
API
API documentation
Lookup, validation, conversion and workflow actions as stable interfaces.
Open docs →ICDICD and OpenAPI
Data contracts, rule IDs, versioning and rollout checklist.
Open ICD →EventsWebhook contract
Callbacks, event order, retries and status return to internal systems.
Open webhooks →EnvSandbox vs production
Separate test/prod environments and cutover rules before live use.
Open sandbox →Integration layers
Batch
Batch processing
Volume scenarios need manifests, retries and monitoring, not one-off uploads.
Batch workflow →BridgePDF/manual bridge
When the input is not clean XML, mapping and review gates matter.
Open bridge →ArtifactsArtifact return
Return final XML/PDF and evidence bundles to the client archive.
Open artifacts →OpsStatus and observability
Correlation IDs, webhook logs and support views for real operations.
Open observability →