Skip to main content

Integrate into your workflow

This page helps you set up your INCERT integration and provides common usage scenarios to guide your implementation.

Set up your integration​

To begin using your tokens for actual data pseudonymisation:

  1. Choose your integration approach: Make direct API calls to https://incert.lu from your application using the endpoints and request structure described in Use the tokens.

  2. Prepare your data: Format your identifiers as a JSON array of strings in the data field, or as a comma-separated CSV string. If you are collaborating with other organisations, ensure all parties have aligned on the same PID (Personal Identifier) format before sending data. Inconsistent formats across organisations will produce inconsistent pseudonyms.

  3. Implement secure token handling: Store tokens using environment variables or secret management systems—never hardcode them.

  4. Test with sample data: Verify your integration works correctly before processing production datasets.

Common use cases​

Depending on your organisation's needs you may use tokens in different ways.

Scenario 1: One-time data sharing. If you need to pseudonymise a dataset once before sharing with a research partner, you might generate a single pseudonymisation token in the Portal, process your dataset through INCERT, and then share the pseudonymised results. This approach works well for discrete, one-off data exchanges where ongoing access isn't required.

Scenario 2: Ongoing data processing. For organisations that regularly pseudonymise data as part of their workflow, consider setting up a project with an appropriate retention period and generating tokens as needed. You could integrate INCERT API calls directly into your data pipeline to automate the pseudonymisation process, regenerating tokens when they expire based on your retention settings.

Scenario 3: Multi-party collaboration. When collaborating with multiple organisations on pseudonymised data, you might create a shared collaboration project and add your partners as members. Each organisation can then generate their own tokens while all parties pseudonymise data using the same project configuration, ensuring consistency across the collaboration.