Knowledge base MessagesEntitiesAttributesCode listsErrors and fixesProcessesRolesReleasesGlossaryEcosystemCompare Validator NL EN

Chain agreements: feedback, correction, chunking, transport, releases

Transport and security: REST, x-api-key, OAuth 2.0, mTLS and x-jws-signature

VB-PUO uses RESTful APIs over HTTPS only, in a push model: the sender takes the initiative. Authentication is via an API key in the x-api-key header or OAuth 2.0 client credentials; mutual TLS (mTLS) is the principle and messages can be digitally signed with the x-jws-signature header.

Steps

Rules and consistency checks

  • Other transport forms (files, e-mail) are not supported by the standard.
  • GitHub issues #102 and #143 concern mTLS set-up; #106 API versioning.

Source: Handleiding paragraaf 2.7 en 7.4

Attribution. Source: SIVI – VB-PUO Standard. Schemas, attribute descriptions and code lists are taken unchanged from the VB-PUO Standard (owned by the Pensioenfederatie, managed by SIVI) and shown with their release and version. Explanations, examples, error descriptions and translations are by WTP Data Lab and are not part of the standard. GitHub Stichting-SIVI/VBPUOdsk · Manual · sivi.org