Feature requests

Add location field to Cards API endpoints
When building custom integrations via the Boomerangme API, there is currently no way to attach a location to card operations. This is possible today through manager accounts (via the Scanner App), but not via API. For agencies and partners building custom integrations, this means location-level reporting is effectively unavailable – every transaction is unattributed at the location level, which breaks a core reporting use case for multi-location merchants. Reference: https://docs.digitalwallet.cards/#tag/cards Current situation Manager accounts → can be assigned a location which adds the location to a transaction via the Scanner App ✅ Custom API integrations → no location field available on any card endpoint ❌ Result: multi-location businesses that need custom integrations (POS, kiosk, checkout flows, in-house apps) lose the ability to segment loyalty performance by location. Proposed solution Add an optional location_id field to the request body schema of all card-related API endpoints, including but not limited to: Add stamp to card Add amount to card Redeem reward Any other card transaction endpoint The field should be optional (not required) so it doesn't break existing integrations. When provided, the transaction should be attributed to that location and appear in the card's transaction history and in location-based analytics – the same behavior that currently exists for manager accounts using the Scanner App. Why this matters Unlocks location-level reporting for every custom integration Brings API parity with what manager accounts can already do Removes a blocker for agencies building integrations for multi-location merchants This is currently a missing key element for any agency or partner building serious integrations.
0
Load More
→