For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

Updated device hash management and event generation

· 3 min read

We have updated the MobileID, ReuseID, and Admin APIs with new device hash management features and device state event generation parameters.

MobileID API​

Generating an event when the device state changes​

You can now control whether you receive an event when the device state changes by passing the generateEvent=true query parameter for the Update device operation.

If generateEvent is omitted, it defaults to false, and no event is generated.

Want to learn more?

To learn more, see the Update device endpoint in our MobileID API reference documentation.

ReuseID API​

Added MobileID device hash management resource​

Our ReuseID API is extended with a new resource for MobileID device hash management.

The new endpoints allow you to retrieve a list of devices associated with a given device hash and lock all devices associated with that hash. You can read more about this in our ReuseID API reference documentation using the links below.

Want to learn more?

To learn more, see the following endpoints in the ReuseID API reference documentation:

Generating an event when the device state changes​

You can now control whether you receive an event when the device state changes by passing the generateEvent=true query parameter for the Update device operation.

If generateEvent is omitted, it defaults to false, and no event is generated.

Want to learn more?

To learn more, see the Update device operation in our ReuseID API reference documentation.

Admin API​

Updated statistics resource​

We have moved the following two operations from the Statistics resource in the Admin API to the MobileID device hash management resource in the ReuseID API:

  • Get devices with device hash
  • Lock devices with device hash

Changed context path for Get device hash statistics​

To align with our other services, we have changed the context path for the Get device hash statistics operation from devicehashes to device-hashes.

Backward compatibility

This context path change is not backward compatible.

  • If your integration calls this operation, then you must update it to use the new device-hashes context path.
  • If you access this operation only through the Signicat Dashboard, then no action is required as the Signicat Dashboard already uses the new context path.