This register is maintained to meet the EU Data Act’s requirement for an up-to-date register, providing details on the data structures, formats, relevant standards, and open interoperability specifications for all exportable data.
Note: this page may be subject to changes.
Last Updated: v.1.0. September 12, 2025.
Structures & formats
- OpenAPI (Swagger) – machine-readable REST description of endpoints.
- Data formats: JSON
- Timestamps: Unix timestamp
- Documents: base64
- Pagination: be aware of pagination. Read more here.
Applied standards and open interoperability specifications
- Penneo applies a RESTful API design, using a standard with clear resource endpoints.
- Penneo uses the JSON data format for simple and universal data exchange.
- Penneo relies on OAuth 2.0 for authentication, implementing a secure, open standard for granting third-party access without sharing passwords.
- Penneo uses TLS 1.2+ to ensure all data transferred is securely encrypted.
Access & authentication
- Please see API Authentication.
- We recommend OAuth API keys grant.
- Organisations have access to data on their own Penneo environment
Exporting data
Through Penneo support:
- The Customer shall provide, or authorize Penneo to create, the necessary API credentials to enable the complete export of the Customer Data.
- Penneo shall upload the exported Customer Data to a mutually agreed-upon secure file-sharing platform.
- Penneo shall provide the individuals designated in the Customer’s Switching Notice with secure credentials to access the exported Customer Data on the agreed-upon platform.
Using the API:
- Authenticate using one of Penneo’s supported authentication methods
- Using the Super API user API credentials allows exports of data on account level.
- Please note that the Super API user solely support GET requests.
- Obtain a list of all casefiles using the GET casefile list endpoint
- For large organisations consider pagination
- For each casefileId use the GET casefile details endpoint
- Casefile, document, signer, and other relevant data can be exported from the response
- Use documentId from the casefile details to obtain the base64 encoded PDF using GET the PDF document as a file
- To identify what folder the casefile is linked to use the GET the folder for the casefile
- Attachments can be identified on the signer using the signerId on the GET the meta data for files
- Using the fileId the file can be downloaded by GET the file
Note 1: See linked documentation for filtration options.
Note 2: It is not possible to retrieve the Active user list with userName, userId, email, and role via API.
Exportable data
Please visit our terms.