Account closure

Sync account closure in both directions: your platform can close the LoginSign connection via API, and LoginSign notifies you via webhook when a user removes your app or when you delete the connection.

1. Developer closes account (API)

When the user closes their account on your platform, call our API to delete the connection so they are also disconnected from LoginSign for your app.

DELETE/api/developer/applications/:appId/users/:connectionId

Requires developer session (cookie). Permanently deletes the user's connection to your app. Your webhook (if set) receives user_account_deleted.

// Example
await fetch(`${API_URL}/api/developer/applications/${appId}/users/${connectionId}`, {
  method: 'DELETE',
  credentials: 'include'
});

2. Webhooks (LoginSign → your server)

Configure a Webhook URL in Settings → Webhook. We POST JSON to it for the following events.

connection_deleted

Sent when the user removes your app from their LoginSign dashboard (or revokes access).

{
  "type": "connection_deleted",
  "connectionId": "clx...",
  "userId": "AB1234",
  "aliasEmail": "x9s8d7@loginsign.com",
  "applicationId": "your-app-id",
  "reason": null,
  "deletedAt": "2025-02-21T12:00:00.000Z"
}

Use this to remove or flag the user on your side (e.g. disable their account, delete local data).

user_account_deleted

Sent when the developer deletes the connection via the API (DELETE above), or when the connection is permanently removed.

{
  "type": "user_account_deleted",
  "applicationId": "your-app-id",
  "connectionId": "clx...",
  "userId": "AB1234",
  "aliasEmail": "x9s8d7@loginsign.com"
}

Sync: delete or anonymize the user on your platform.

Summary

  • User removes your app in LoginSign → you receive connection_deleted.
  • You call DELETE (user closed account on your site) → connection is removed and you receive user_account_deleted.

Implement your webhook endpoint to accept POST with Content-Type: application/json and respond with 2xx so we don't retry unnecessarily.