GET {{baseURL}}/pay-api/v1/devices/{{deviceId}}
This endpoint retrieves the specified device.
See Also:
To retrieve devices, see GET /pay-api/v1/devices.
To create or update a device, see POST /pay-api/v1/devices.
To generate a tap-to-pay token for a device, see POST /pay-api/v1/devices/tap-to-pay/jwt.
To activate tap-to-pay for a device, see POST /pay-api/v1/devices/{deviceId}/tap-to-pay/activate.
- Mock serverhttps://developer.flute.com/_mock/api-reference/pay-api/v1/devices/{deviceId}
- Sandbox environmenthttps://sandbox.api.flute.com/pay-api/v1/devices/{deviceId}
- Production environmenthttps://api.flute.com/pay-api/v1/devices/{deviceId}
curl -i -X GET \
https://developer.flute.com/_mock/api-reference/pay-api/v1/devices/7aafd09f-b3e6-43fb-b815-5db3bf7f1454 \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'OK
Indicates the device identifier.
Example: 7aafd09f-b3e6-43fb-b815-5db3bf7f1451
Indicates the last login time (in an ISO 8601 date-time UTC format).
Example: 2026-01-19T14:27:02.767105Z
Indicates the API key name being used.
Example: Peppared's Cafe Key
Indicates the tap to pay status.
Valid values are:
| Tap To Pay status |
|---|
| Active |
| Approved |
| Denied |
| Inactive |
| Requested |
Example: Active
Indicates the tap to pay status identifier.
Valid values are:
| Id | Status |
|---|---|
| 0 | Inactive |
| 1 | Requested |
| 2 | Approved |
| 3 | Active |
| 4 | Denied |
Example: 2
Indicates tap to pay feature is enabled.
If true, tap to pay feature is enabled.
If false, tap to pay feature is not enabled.
Example: true
{ "deviceId": "7aafd09f-b3e6-43fb-b815-5db3bf7f1451", "deviceName": "iPhone12,1", "lastLoginAt": "2026-01-19T14:27:02.767105Z", "apiKeyName": "Peppared's Cafe Key", "tapToPayStatus": "Active", "tapToPayStatusId": 2, "tapToPayEnabled": true, "userProfiles": [ { "id": "04103b7f-c2fc-444b-b1ab-93eee3aec815", "firstName": "Alexandro", "lastName": "Peppared", "email": "peppared@example.com" } ] }