Prerequisites

Some steps in the onboarding are only necessary if the party to be onboarded is only interested in sending messages It is mentioned in each listed prerequisite if this is the case A PEPPOL Participant for receiving documents All clients interested in receiving documents must have a valid participant registered in the PEPPOL network The participant can be registered in any SMP of your choosing such as Tickstar or ELMA Parties that are only interested in sending documents may ignore this step A Heimdall client for authentication All requests made to Common Accesspoint are authenticated using heimdall bearer tokens Any clients using the API must therefore produce a valid Heimdall client which they can use to authenticate themselves Receivers defined in Common Parties The CAP API uses Common Parties for managing data about receivers and to which account their messages should be stored A receiving participant may for example want to define multiple accounts to store data on all using the same participant Receiver information is refreshed from Common Parties periodically Any inbound message whose recipient account cannot be determined upon arrival due to missing or wrong configuration is stored on a placeholder account until further notice Once the receiver information is available the message in question is then moved to its rightful owner Parties that are only interested in sending documents may ignore this step An account This step is handled manually by the API developers Ask the developers for help and let them know what configuration you would like for the account However accounts can only have one assigned country code at a time If you need to transact on behalf of multiple countries we recommend that you create one account per country