Update customer mapping
Customer
Update customer mapping
v1 is deprecated — use the v2 endpoint instead. Re-links your customer IDs to existing Swipe records in bulk. Use this after changing IDs in your own system, so future calls don’t create duplicate customers.
POST
Update customer mapping
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is an API key from the API Integration section of your dashboard. Keys are scoped to the company they are generated in — for testing, add a separate test company and generate the key there, so requests never touch your real books.
Body
application/json

