Skip to main content
POST
Create access control credential by hex value and type

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 create an access control credential by hex value and type.

credentialType
enum<string>
Available options:
STANDARD_CSN,
RHOMBUS_SECURE_CSN,
RHOMBUS_SECURE_MOBILE,
PIN_CODE,
WIEGAND_H10301,
WIEGAND_H10304,
WIEGAND_H10302,
WIEGAND_D10202,
WIEGAND_64BIT_RAW,
HID_CORP1000_STD_35,
HID_CORP1000_STD_48,
QR_CODE_STATIC,
CUSTOM
endDateEpochSecExclusive
integer<int64> | null
int64

End date in epoch seconds (exclusive)

Example:

1672531200

hexValue
string | null

Hex value of the credential

Example:

"1234567890ABCDEF"

littleEndian
boolean | null

Only needed when creating Wiegand credentials

numValueBits
integer<int32> | null
int32

Only needed when creating Wiegand credentials

startDateEpochSecInclusive
integer<int64> | null
int64

Start date in epoch seconds (inclusive)

Example:

1640995200

userUuid
string<RUUID> | null
RUUID

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

Response

200 - application/json

OK

Response for access control credential creation by hex value and type.

credential
object

Credentials assigned to the pass.

Last modified on August 3, 2026