Skip to main content
POST
Refresh a device’s authentication token. The old token is revoked and a new token is returned. This allows devices to rotate their credentials without requiring a rebind operation.
This endpoint requires a device token, not an API key. The device must use its current valid token to request a new one.
string
required
The device’s unique identifier (e.g., dev_abc123). Must match the device associated with the token.

Token Lifecycle

When to Refresh

We recommend refreshing tokens proactively rather than waiting for expiration. Consider refreshing:
  • Every 7-14 days during normal operation
  • After a firmware update
  • If you suspect the token may have been compromised

Security Notes

  • Only one valid token exists per device at any time
  • The old token is immediately invalidated when refreshed
  • If a refresh fails, the old token remains valid
  • Unbinding a device revokes the token permanently
The new device token is only shown once in the response. Store it securely on the device immediately. If lost, you must unbind and rebind the device to get a new token.