Data deletion callback

#The endpoint

The data deletion callback is a single HTTPS endpoint that accepts a signed POST request from the calling platform and returns a JSON confirmation.

It is also reachable over GET with a ?code= query parameter so users can look up the status of a deletion request — the lookup tool further down this page demonstrates that.

#How the flow works

• A user removes the DynamicCRM app from the connected platform (for example, in their Facebook app settings).
• The platform sends a signed request to the callback URL identifying the user.
• Our server verifies the signature, queues the user’s data for deletion, and generates a unique confirmation code.
• We respond with a JSON body containing a status URL and the confirmation code.
• The user can visit the status URL at any time to confirm the request was received and completed.

#Request parameters

The platform sends a single field, signed_request, as form-encoded POST data. Once decoded and verified, the payload contains:

#Verifying the request

Before acting on a request, split the signed_request on the . separator and validate the signature against your app secret using a constant-time comparison.

// POST /data-deletion/callback
const [sig, payload] = signedRequest.split('.');
const data = JSON.parse(base64urlDecode(payload));

// Recompute the signature with your app secret
const expected = hmacSha256(payload, APP_SECRET);
if (!timingSafeEqual(expected, base64urlDecode(sig))) {
  return res.status(400).send('Invalid signature');
}

const userId = data.user_id;
await enqueueDeletion(userId);

#Response format

After queuing the deletion, respond with HTTP 200 and a JSON body containing exactly two fields:

{
  "url": "https://melwide.dynamiccrm.com.au/data-deletion-callback?code=DC-7Q2K9X",
  "confirmation_code": "DC-7Q2K9X"
}

#Check a request

Users can confirm the status of a deletion request using the confirmation code they received. Enter a code below to see a sample status response.