Skip to main content
POST
/
api
/
badgereader
/
delete
Delete badge reader
curl --request POST \
  --url https://api2.rhombussystems.com/api/badgereader/delete \
  --header 'Content-Type: application/json' \
  --header 'x-auth-apikey: <api-key>' \
  --header 'x-auth-scheme: <x-auth-scheme>' \
  --data '
{
  "badgeReaderUuid": "AAAAAAAAAAAAAAAAAAAAAA",
  "mummify": false
}
'
{
  "error": true,
  "errorMsg": "<string>",
  "responseStatus": "BASIC_AUTH_FAILED",
  "warningMsg": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://api-docs.rhombus.community/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
x-auth-apikey
string
header
required

Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).

Headers

​
x-auth-scheme
enum<string>
default:api-token
required

Authentication scheme identifier. Use api-token for standard API key authentication, partner-api-token for partner API key authentication. Must be paired with the x-auth-apikey header containing your API key.

Available options:
api-token,
api,
partner-api-token,
partner-api

Body

application/json

Request to delete a badge reader device.

​
badgeReaderUuid
string<RUUID> | null
required

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

​
mummify
boolean | null
required

Whether to mummify the device instead of hard delete

Example:

false

Response

200 - application/json

OK

Response from deleting a badge reader device.

​
error
boolean | null
​
errorMsg
string | null
​
responseStatus
enum<string>

Status of the unregister operation

Available options:
BASIC_AUTH_FAILED,
PASSWORD_MISMATCH,
SAME_PASSWORD,
USER_EXISTS,
USER_NOT_FOUND,
DEVICE_NOT_FOUND,
POLICY_NOT_FOUND,
LOCATION_NOT_FOUND,
ORG_NOT_FOUND,
BAD_INPUT,
SUCCESS,
PASSWORD_TOO_SHORT
​
warningMsg
string | null
Last modified on May 7, 2026