Skip to main content
POST
/
api
/
accesscontrol
/
updateWiegandCredential
Update Wiegand credential
curl --request POST \
  --url https://api2.rhombussystems.com/api/accesscontrol/updateWiegandCredential \
  --header 'Content-Type: application/json' \
  --header 'x-auth-apikey: <api-key>' \
  --header 'x-auth-scheme: <x-auth-scheme>' \
  --data '
{
  "credentialUuid": "AAAAAAAAAAAAAAAAAAAAAA",
  "endDateEpochSecExclusive": 123,
  "startDateEpochSecInclusive": 123
}
'
{
  "credential": {
    "createdAtMillis": 123,
    "endDateEpochSecExclusive": 123,
    "lastUsedAccessControlledDoorUuid": "AAAAAAAAAAAAAAAAAAAAAA",
    "lastUsedAtMillis": 123,
    "lastUsedLocationUuid": "AAAAAAAAAAAAAAAAAAAAAA",
    "lowercaseHexValue": "<string>",
    "managedCredUuid": "AAAAAAAAAAAAAAAAAAAAAA",
    "note": "<string>",
    "orgUuid": "AAAAAAAAAAAAAAAAAAAAAA",
    "startDateEpochSecInclusive": 123,
    "updatedAtMillis": 123,
    "userUuid": "AAAAAAAAAAAAAAAAAAAAAA",
    "uuid": "AAAAAAAAAAAAAAAAAAAAAA",
    "value": "<string>"
  }
}

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 update a Wiegand credential.

​
credentialUuid
string<RUUID> | null

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

​
endDateEpochSecExclusive
integer<int64> | null
​
startDateEpochSecInclusive
integer<int64> | null

Response

200 - application/json

OK

Response containing the updated Wiegand credential.

​
credential
object

Updated Wiegand credential details

Last modified on June 6, 2026