Synchronisation

This module groups all synchronization areas between LoginSign and your platform.

Scope

1. Account Deletion Sync

If a user deletes their account on your platform, call LoginSign's delete endpoint to remove the corresponding connection.

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

Full payload/event examples are available in Account Deletion.

2. Webhook Events (LoginSign -> your backend)

Configure your webhook endpoint in the developer portal to receive state changes.

  • connection_deleted - user removed your app from LoginSign.
  • user_account_deleted - connection was removed by API/developer action.
  • email_changed - primary user email changed and must be synced on your side.

3. OAuth token error handling

During token exchange, LoginSign can return invalid_grant if the authorization code is expired, invalid, already used, or the redirect URI does not match.

{
  "error": "invalid_grant",
  "error_description": "The authorization code has expired"
}

Recommended handling

  • Start a fresh OAuth flow and request a new authorization code.
  • Ensure redirect_uri is identical between authorize and token exchange.
  • Use every authorization code only once.
  • Exchange the code immediately after callback.

4. Related docs