Request Customer Anonymization | NaviPartner

Request anonymization of a customer’s personal data for GDPR compliance.

This endpoint supports three different ways to identify the customer for anonymization:

Option 1: Customer Number Only

Send only customerNo in the request body
Use for company-level anonymization when no specific contact needs to be identified
Example: { "customerNo": "C00001" }

Option 2: Customer Number with Contact Number

Send both customerNo and contactNo in the request body
Use for person-level anonymization when the customer is linked to a specific contact
Example: { "customerNo": "C00001", "contactNo": "CT00001" }

Option 3: Email Address Only

Send only email in the request body
The system will locate the customer using the email address
Example: { "email": "customer@example.com" }

The anonymization process will:

Verify if the customer exists in the system
Check if anonymization is allowed (e.g., no active memberships or pending transactions)
Create an anonymization request entry for audit purposes
Return the status and relevant identifiers

Important Notes:

The customer must not have any active memberships or pending transactions
The anonymization process is irreversible once executed
A response code will indicate the reason if anonymization is not possible
When using email, customer records must exist

Use Cases:

GDPR “Right to be Forgotten” requests
Customer account closure with data removal
Self-service customer data removal via email
Compliance with data retention policies

Request anonymization of a customer's personal data for GDPR compliance. This endpoint supports three different ways to identify the customer for anonymization: **Option 1: Customer Number Only** - Send only `customerNo` in the request body - Use for company-level anonymization when no specific contact needs to be identified - Example: `{ "customerNo": "C00001" }` **Option 2: Customer Number with Contact Number** - Send both `customerNo` and `contactNo` in the request body - Use for person-level anonymization when the customer is linked to a specific contact - Example: `{ "customerNo": "C00001", "contactNo": "CT00001" }` **Option 3: Email Address Only** - Send only `email` in the request body - The system will locate the customer using the email address - Example: `{ "email": "customer@example.com" }` The anonymization process will: - Verify if the customer exists in the system - Check if anonymization is allowed (e.g., no active memberships or pending transactions) - Create an anonymization request entry for audit purposes - Return the status and relevant identifiers **Important Notes:** - The customer must not have any active memberships or pending transactions - The anonymization process is irreversible once executed - A response code will indicate the reason if anonymization is not possible - When using email, customer records must exist **Use Cases:** - GDPR "Right to be Forgotten" requests - Customer account closure with data removal - Self-service customer data removal via email - Compliance with data retention policies

Authentication

x-np-api-keystring

API Key authentication via header

Path parameters

tenantstringRequired

Your Entra Tenant ID. More details.

environmentstringRequired

Your Business Central Environment. More details.

companystringRequired

Your Business Central Company. More details.

Request

This endpoint expects an object.

customerNostringOptional

The customer number. Required unless using email-based lookup.

contactNostringOptional

The contact number. Optional; use together with customerNo for person-level anonymization.

emailstringOptional

The email address. Use alone to identify customer by email.

Response

This endpoint returns an object.

successboolean

Indicates whether the anonymization request was created successfully

messagestring

Detailed message describing the result of the anonymization request

customerNostringOptional

The customer number that was processed (included when applicable)