External movement on a segregated wallet
The activity sync detected an on-chain movement of a segregated wallet that did not go through the platform (expected under client custody, e.g. after importing or exporting the key). The wallet’s activity record stays complete either way.
WEBHOOK
Authorizations
Session JWT (from register/login) or API key (pk_...).
X-API-Key: <token> is accepted as an alternative header.
Response
200
Return any 2xx to acknowledge the delivery.
Last modified on July 18, 2026