Skip to main content

Data fields

Every piece of data on a Credential is stored as a named field. Fields are divided into two categories:

  • Providable fields (manual_input: true) — values you supply when ordering a Credential via CredentialOrderV1.
  • System-populated fields (manual_input: false) — values the system sets automatically (card numbers, RFID data, Tenant info, Number Ranges). You cannot set these when ordering.

Not every Template uses every field. Call CredentialTemplatesV2 to get the exact list of fields a Template requires before ordering. All requests must be authenticated — see Authentication.


Providable fields

These fields can be included in the data array when calling CredentialOrderV1. Use the value key that matches the field's type — see type matching.

Person

NameTypeDescription
personFirstNamestringFirst name
personLastNamestringLast name
personMiddleNamestringMiddle name
personFullNamestringFull name (alternative to separate first/last)
personEmailstringEmail address
personPhoneNumberstringPhone number
personMobilePhoneNumberstringMobile phone number
personEmployeeNostringEmployee number
personPersonalNostringPersonal identification number
personGenderstringGender
personCountryCodestringTwo-letter country code (e.g. NO)
personCountrystringCountry name
personEducationCodestringEducation or qualification code
personPinstringPIN code
personDepartmentstringDepartment or unit

Company

NameTypeDescription
companyNamestringName of the issuing company

Card

NameTypeDescription
cardValidUntilDatedateCredential expiry date
cardNumberManualstringManually assigned card number
cardBarcodestringBarcode value printed on the card

Order

NameTypeDescription
orderCostCentrestringCost center for billing purposes
orderPartnerIdstringPartner system identifier

User (ordering user)

NameTypeDescription
userNamestringName of the user placing the order
userEmailstringEmail of the user placing the order
userPhonestringPhone of the user placing the order

Delivery address

Used when the Credential should be physically shipped to an address.

NameTypeDescription
addressReceiverstringRecipient name
addressAttentionstringAttention line (c/o)
addressAddress1stringStreet address line 1
addressAddress2stringStreet address line 2
addressPostCodestringPostal code
addressCitystringCity
addressCountrystringCountry

Messaging

NameTypeDescription
messageToAccessVendorstringMessage passed to the access control vendor at production time

Custom calculations

String fields that can be used for Template formulas and partner-specific calculated values.

NameType
customCalc1customCalc10string

Extra fields

Arbitrary string and date fields for partner-specific data not covered by named fields.

NameType
extra1extra31string
extraDate1extraDate5date

System-populated fields

These fields are set automatically by Breeze. They are read-only when ordering — values you provide for them will be ignored.

Images

Although these are system-populated in manual form workflows, you can supply image fields via the API using base64_value (Base64-encoded image) or url_value (publicly accessible URL, max 5 MB). The system downloads and stores the image.

NameTypeDescription
personPhoto1bufferPrimary person photo
personPhoto2bufferSecondary person photo
personSignaturebufferSignature image
companyLogobufferCompany logo
companyLogoFrontbufferCompany logo — front of card (auto-sourced from Tenant)
companyLogoBackbufferCompany logo — back of card (auto-sourced from Tenant)
cardFrontPreviewbufferGenerated preview of the front of the card
cardBackPreviewbufferGenerated preview of the back of the card

Card system fields

Set by Breeze at production time.

NameTypeDescription
cardNumberstringSystem-assigned card number
cardSpecIdstringCard specification identifier
cardSpecNamestringCard specification name
cardOrderDatedateDate the Credential was ordered
credentialNumberstringHuman-readable Credential number (same as credential_number on the Credential type)

Tenant

Automatically populated from the Tenant context.

NameTypeDescription
tenantIdstringTenant ID
tenantNumberstringTenant number
tenantNamestringTenant name
tenantExternalRefstringTenant external reference

Requester

Populated from the authenticated API user.

NameTypeDescription
requesterIdstringID of the user who placed the order
requesterFirstNamestringFirst name of the requester
requesterLastNamestringLast name of the requester
requesterEmailstringEmail of the requester
requesterPhonestringPhone of the requester

Number Ranges

Populated from Number Range configurations on the Template. Three independent ranges are supported.

NameTypeDescription
range1SequencestringRange 1 — sequence number
range1FullSequencestringRange 1 — full formatted sequence
range1VersionNumberstringRange 1 — version number
range1PrefixstringRange 1 — prefix
range1SuffixstringRange 1 — suffix
range1SiteCodestringRange 1 — site code
range1Formula1range1Formula3stringRange 1 — calculated formula outputs
range2Sequencerange2Formula3stringRange 2 — same set of fields
range3Sequencerange3Formula3stringRange 3 — same set of fields

Template formulas

Calculated outputs from Template-level formulas.

NameType
templateFormula1templateFormula3string

RFID card serial number (CSN)

Populated when the Credential is encoded with an RFID chip. Twenty-four format variants covering HF and LF frequencies in different byte orders and vendor encodings.

NameDescription
uidHfHexMsbHF — Hex MSB
uidHfHexLsbHF — Hex LSB
uidHfDecMsbHF — Decimal MSB
uidHfDecLsbHF — Decimal LSB
uidHfRcoHF — RCO format
uidHfArxHF — ARX format
uidHfSchneiderHF — Schneider format
uidHfMsb5bDecHF — 5-byte decimal
uidHfMsbFirst4bDecHF — first 4 bytes MSB decimal
uidHfMsbLast4bDecHF — last 4 bytes MSB decimal
uidHfLsbFirst4bDecHF — first 4 bytes LSB decimal
uidHfLsbLast4bDecHF — last 4 bytes LSB decimal
uidHfHs24HF — HS24 format
uidLfHexMsbLF — Hex MSB
uidLfHexLsbLF — Hex LSB
uidLfDecMsbLF — Decimal MSB
uidLfDecLsbLF — Decimal LSB
uidLfSolidLF — Solid format
uidLfBewator2010LF — Bewator 2010
uidLfBewatorEntroLF — Bewator Entro
uidLfBravidaLF — Bravida format
uidLfRcoLF — RCO format
uidLfH10304LF — HID Prox H10304
uidLfAxemaLF — Axema format

All RFID fields are string type.


Type matching

When providing a field value in the data array, use exactly one value key matching the field's type:

Field typeValue key
stringstring_value
numbernumber_value
booleanbool_value
datedate_value — ISO 8601 format: 2035-12-31T12:00:00.000Z
bufferbase64_value (Base64-encoded image) or url_value (image URL)

Providing the wrong key for a field's type will return a BAD_USER_INPUT error.

See also