EN
EN
Notices can be transmitted to the Vermittlungsdienst via the REST-API of the Vermittlungsdienst or via the eDelivery-Network PEPPOL.
The REST API and the associated documentation for the existing endpoints are available at https://ozg-vermittlungsdienst.de.
To use the API, access data must be requested once. Authorization takes place via OAuth 2.0.
A new account is set up via the self-service portal (production environment: https://self-service.datenservice-oeffentlicher-einkauf.de). An account can be created in the portal by specifying an e-mail address and a password. After confirming the e-mail address, the user can log in and complete the application form for a new VD account. A separate user is required for each awarding platform.
Once the user has been created, an authentication email containing a link for authentication and password creation is sent to the specified user email address for verification. If, for example, 10 accounts are requested for an environment, 10 individual e-mail addresses are also required. The e-mail address is used to retrieve the tokens that are required for unique authentication with the account. The email address must therefore be unique.
The link is valid for 10 days.
After clicking on the link, instructions for creating a password appear.
An access token and a refresh token can be generated using the API with the access data created.
Please note that one access must be requested per development environment (preview, staging, production). The access data is not synchronized. Preview and Staging accounts can be requested in the corresponding self-service portal environment.
The endpoint POST /api/token is used with the parameters username and password to be passed in order to obtain an access_token and refresh_token. The username is the specified e-mail address.
The access_token is valid for 24 hours and can be used for authorization for all subsequent requests in the header as follows: Authorization: Bearer <<access_token>>. After 24 hours, a new authentication is required. To avoid regular authentication with username and password, a new access_token can be generated using the refresh_token and the endpoint POST /api/token/refresh without having to perform a new full authentication.
Requesting a new token does not invalidate the previous token.
Example response of the endpoints POST /api/token and POST /api/token/refresh:
{
"access_token": "eyJhbGciOikpXVCJ9.eyJzMDIyfQ.SflKxwRJSM",
"expires_in": 36000,
"refresh_expires_in": 36000,
"refresh_token": "eyJhbGciOikpXVCJ9.eyJzMDIyfQ.SflKxwRJSM",
"token_type": "Bearer",
"not-before-policy": 0,
"session_state": "e65f24ae-4e90-4635-8ae7-4fb89fe471bf",
"scope": "profile email"
}
Further information on the concept of the refresh token and instructions for implementation are available at https://auth0.com/blog/refresh-tokens-what-are-they-and-when-to-use-them/
Public procurement platforms can also submit notices to the Data Service for Public Procurement in Germany via the Peppol infrastructure.
Systems registered in the Peppol infrastructure can send notices to the addressee with the Peppol ID "0204:994-DOEVD-83" (production) using the Peppol profile "P008 - Publish Notices ".
Communication takes place via the use of a pre-award-capable AccessPoint, which is either
Important: Full pre-award capability of the AccessPoint includes support for "REM Evidence ", as described in the documentation at the following link: Peppol BIS eDelivery Guide for Pre-Award v1.3
Questions regarding registration must be clarified via a Peppol-Authority: List of Peppol Authorities
The primary interface for the transmission of notices is the PEPPOL network. Notices can be transmitted as follows:
0204:994-doevd-83.0204:994-doevdtest-85urn:fdc:peppol.eu:prac:bis:p008:1.2
urn:fdc:peppol.eu:prac:trns:t015:1.2).urn:fdc:peppol.eu:prac:trns:t016:1.2).oeffentliche-vergabe-peppoloeffentlich-vergabe-peppol-test.PEPPOL messages consist of several layers that are defined by different standards. Each layer encloses the data of the next layer and extends it with specific aspects that are required. The layers from the outside in:
META-INF/ASiCManifest.xml, which lists all contained files with checksums;RootFile=true in META-INF/ASiCManifest.xml. This file is the business or process document that is to be processed;urn:fdc:peppol.eu:prac:trns:t015:1.2) to publish notices;urn:fdc:peppol.eu:prac:trns:t016:1.1);The PEPPOL access point for the Vermittlungsdienst and the announcement service is operated by the Procurement Office of the Federal Ministry of the Interior (BeschA).
call up the self-service portal of the desired environment (can be found under System environments in the Self Service Portal line).
click on 'Forgot password?
enter your e-mail address and click on 'Send'.
the message 'You should receive an e-mail with further instructions shortly' is displayed.
check the emails: A link to reset the login information is included in the email.
click on 'Link to reset credentials'.
the user is redirected to the 'Update password' page
.
enter and confirm the new password and click on 'Submit'.
The password must consist of at least 8 characters, contain 1 capital letter and 1 number.
the password must be stored in the software of the specialist procedure manufacturer to ensure that the connection with the Vermittlungsdienst works.
To delete an access, send an e-mail to the Data Service for Public Procurement in Germany support team support@datenservice-oeffentlicher-einkauf.de.
The e-mail must contain the following information:
After checking the data provided in the e-mail, the access is deleted and a confirmation is sent by e-mail.