List existing readers via GET /v1/terminal/readers with optional location filter to identify the reader to move
POST /v1/terminal/readers/<reader_id> with location=<new_location_id> to reassign the reader; this immediately updates the reader's location association
Optionally include label=<new_label> in the same request to rename the reader for clarity in multi-location deployments
After the update, any connection tokens generated with the old location will no longer allow connecting to this reader; generate a new connection token scoped to the new location
If you are using server-driven integration without location-scoped tokens, verify your POS application is updated to target the correct reader id at the new location
Known gotchas
Moving a reader to a new location does not automatically disconnect currently connected POS sessions; existing SDK connections will continue until they time out or are explicitly disconnected
If the reader is mid-transaction when the location is updated, the transaction is not affected; the location change takes effect for subsequent connection token requests
Location objects are permanent and cannot be deleted via the API once created; use descriptive names to avoid confusion in multi-location deployments
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?