Skip to main content

Metadata Properties Reference

The metadata properties endpoint provides a comprehensive reference of all available data fields and check identifiers used in the Otentica verification system.

Endpoint​

GET https://api.otentica.nl/check-metadata/properties
Accept: application/json
info

This endpoint is publicly accessible and does not require authentication. It returns the complete schema of available properties that can be returned by various verification checks.

Response Structure​

The endpoint returns a JSON object containing property definitions organized by check type. Each property includes:

  • Property name: The field identifier used in API responses
  • Data type: The type of data (STRING, LIST, FILE, DATE, etc.)
  • Check context: Which verification check produces this property
  • Validation source: The third-party service or method used for verification

Property Categories​

1. Healthcare Professional Data​

Properties related to healthcare professional registrations in the Netherlands:

PropertyTypeDescriptionCheck Identifier
bigRegistrationsLISTBIG registry registrationsbig-data
bigProfessionalGroupSTRINGProfessional category (e.g., Arts, Tandarts)big-data
bigNumberSTRINGBIG registration numberbig-data
bigSpecialismsLISTMedical specializationsbig-data
bigLimitationsLISTProfessional practice limitationsbig-data
bigJudgmentsLISTDisciplinary judgmentsbig-data
bigVisionsLISTProfessional competenciesbig-data
skjRegistrationsLISTSKJ registry registrationsskj-data
skjProfessionalGroupSTRINGYouth care professional categoryskj-data
skjNumberSTRINGSKJ registration numberskj-data

2. Identity Data​

Personal identification information verified through various sources:

PropertyTypeDescriptionCheck Identifier
firstNameSTRINGFirst nameidentity-data
lastNameSTRINGLast nameidentity-data
lastNamePrefixSTRINGSurname prefix (e.g., "van", "de")identity-data
initialsSTRINGName initialsidentity-data
dateOfBirthDATEDate of birthidentity-data
genderSTRINGGender (MALE/FEMALE/OTHER)identity-data
personalNumberSTRINGBSN (Dutch citizen service number)identity-document-v2

3. Address Data​

Residential and correspondence address information:

PropertyTypeDescriptionCheck Identifier
streetSTRINGStreet nameidentity-data
houseNumberSTRINGHouse numberidentity-data
houseNumberSuffixSTRINGHouse number additionidentity-data
postalCodeSTRINGPostal codeidentity-data
citySTRINGCityidentity-data
countryCodeSTRINGISO country codeidentity-data

4. Contact Information​

Communication details:

PropertyTypeDescriptionCheck Identifier
emailSTRINGEmail addresscorrespondence-data
phoneSTRINGPhone numbercorrespondence-data
websiteUrlSTRINGWebsite URLcorrespondence-data
linkedinUrlSTRINGLinkedIn profile URLcorrespondence-data

websiteUrl and linkedinUrl are collected only when enabled via the collectWebsiteUrl / collectLinkedInUrl configuration flags on the correspondence-data check. Both fields support an explicit "I don't have this" state: when a candidate opts out, the value is null and this is recorded as a deliberate response, not missing data.

URLs must be fully qualified (e.g. https://www.example.com). LinkedIn URLs are validated to point to linkedin.com.

5. Identity Document Data​

Information from identity verification documents:

PropertyTypeDescriptionCheck Identifier
identityDocumentFILEFront of ID documentidentity-document-v2
identityDocumentBacksideFILEBack of ID documentidentity-document-v2
selfieFILESelfie photo for verificationidentity-document-v2
identityDocumentTypeSTRINGType (PASSPORT/ID_CARD)identity-document-v2
identityDocumentNumberSTRINGDocument numberidentity-document-v2
identityDocumentDateOfExpiryDATEExpiry dateidentity-document-v2
nationalitySTRINGNationality (ISO code)identity-document-v2

6. Company Data​

Business and employer information:

PropertyTypeDescriptionCheck Identifier
companyNameSTRINGCompany namecompany-data
kvkNumberSTRINGKvK (Chamber of Commerce) numbercompany-data
companyAddressesLISTCompany addressescompany-data
companyRsinSTRINGRSIN of the companycompany-data
companyLegalFormSTRINGLegal form of the companycompany-data
sbiDescriptionsLISTList of the SBI codes including descriptionscompany-data
sbiCodesLISTList of the SBI codes without the descriptionscompany-data

7. Bank Account Data​

Financial account verification:

PropertyTypeDescriptionCheck Identifier
personalIbanSTRINGPersonal IBANbank-data
personalIbanNameSTRINGPersonal account holder namebank-data
personalIbanCountrySTRINGPersonal account countrybank-data
businessIbanSTRINGBusiness IBANbank-data
businessIbanNameSTRINGBusiness account holder namebank-data
businessIbanCountrySTRINGBusiness account countrybank-data
Business account enforcement

When the bank-data check is configured with checkBusinessAccount: true and the candidate submits a personal IBAN, the API returns the remark business-personal-iban-not-allowed in the response. This remark is returned at the API level and is also reflected in the PDF report and the Otentica dashboard.

8. Credit Check Data​

Credit assessment returned as part of the company-data check when enableCreditCheck: true is configured. Data is sourced from an external data provider; no provider name is returned in the API response.

Availability

These fields are only returned when company-data is configured with checkLevel: "EXTENDED" or checkLevel: "FULL" and enableCreditCheck: true.

PropertyTypeDescriptionCheck Identifier
creditCheckResultSTRINGCurrent credit rating label (e.g. A, B, C, or NOT_RATED)company-data
creditCheckDescriptionSTRINGHuman-readable description of the current ratingcompany-data
creditLimitCurrencySTRINGISO 4217 currency code for the credit limitcompany-data
creditLimitValueSTRINGCredit limit amountcompany-data
creditScoreSTRINGNumeric credit scorecompany-data
creditScoreDescriptionSTRINGDescription of the credit scorecompany-data
creditPodSTRINGProbability of defaultcompany-data
creditRatingChangeDateSTRINGDate of the most recent rating changecompany-data
creditPreviousResultSTRINGPrevious credit rating labelcompany-data
creditPreviousDescriptionSTRINGHuman-readable description of the previous ratingcompany-data
creditPreviousLimitCurrencySTRINGISO 4217 currency code for the previous credit limitcompany-data
creditPreviousLimitValueSTRINGPrevious credit limit amountcompany-data
creditPreviousProviderDescriptionSTRINGProvider description for the previous rating periodcompany-data

When no credit rating is available for a company, creditCheckResult returns NOT_RATED. In this case creditLimitValue, creditScore, and creditPod may be null.

10. Education & Diploma Data​

Educational qualifications and certifications:

PropertyTypeDescriptionCheck Identifier
diplomasLISTList of diploma objectsdiploma-data
unverifiedDiplomasLISTUploaded certificatesunverified-diploma-data

Each diploma object contains:

  • type: Type of qualification (DIPLOMA/CERTIFICATE)
  • title: Diploma title
  • description: Detailed description
  • issuer: Issuing institution
  • level: Education level
  • validFrom: Start date (if applicable)
  • validUntil: Expiry date (if applicable)
  • verifiedOn: Verification timestamp
  • verifier: Verification source (e.g., "duo", "emrex")
  • verificationStatus: Status of verification
  • fileId: Associated document file ID

11. Integrity Data​

Background and integrity check information:

PropertyTypeDescriptionCheck Identifier
vogDocumentFILEVOG (Certificate of Good Conduct)vog-data
vogDocumentDateDATEVOG issue datevog-data
vogDocumentNumberSTRINGVOG document numbervog-data
vogScreeningProfileSTRINGVOG screening profilevog-data

12. Employment References​

Reference check data:

PropertyTypeDescriptionCheck Identifier
referencesLISTList of reference objectsreference-data

Each reference contains:

  • referenceName: Reference person name
  • referenceEmail: Reference contact email
  • referenceCompany: Reference company
  • referenceRelation: Relationship to candidate
  • referenceResponse: Reference feedback

13. PEP Check Data​

Result fields from the pep-check. Data is sourced from an external data provider; no provider name is returned in the API response.

PropertyTypeValues / DescriptionCheck Identifier
pepCheckResultSTRINGPEP / NOT_PEP / UNCERTAINpep-check
pepCheckScoreNUMERICMatch score: 0.0 (no match) to 1.0 (full match)pep-check
pepCheckSourceSTRINGAudit — identifier of the external data sourcepep-check
pepCheckDateSTRINGAudit — date on which the check was performedpep-check

Scores at or above the configured threshold (default: 0.7) trigger a manual review flag. The threshold is configuration-driven per client.

14. Sanctions Check Data​

Result fields from the sanctions-check. Data is sourced from an external data provider; no provider name is returned in the API response.

PropertyTypeValues / DescriptionCheck Identifier
sanctionsCheckResultSTRINGSANCTIONED / NOT_SANCTIONED / UNCERTAINsanctions-check
sanctionsCheckScoreNUMERICMatch score: 0.0 (no match) to 1.0 (full match)sanctions-check
sanctionsCheckSourceSTRINGAudit — identifier of the external data sourcesanctions-check
sanctionsCheckDateSTRINGAudit — date on which the check was performedsanctions-check

Scores at or above the configured threshold (default: 0.7) trigger a manual review flag. The threshold is configuration-driven per client.

Data Types​

The API uses the following data types for properties:

TypeDescriptionExample
STRINGText value"John Doe"
LISTArray of values or objects["value1", "value2"]
FILEFile reference UUID"e7e5e957-f010-4de7-9423-fe7581965192"
DATEISO 8601 date format"2024-01-15" or "2024-01-15T10:30:00Z"

Usage Example​

// Fetch available properties
async function getMetadataProperties() {
const response = await fetch(
'https://api.otentica.nl/check-metadata/properties',
{
headers: {
'Accept': 'application/json'
}
}
);

const properties = await response.json();
return properties;
}

// Map properties to check results
function mapCheckResultToProperties(checkResult, properties) {
const mappedData = {};

checkResult.results.forEach(result => {
// Use the property metadata to understand the data type
const propertyMeta = properties[result.fieldName];

if (propertyMeta) {
mappedData[result.fieldName] = {
value: result.value,
type: propertyMeta.type,
verified: result.verified,
verifiedBy: result.verifiedBy,
verifiedOn: result.verifiedOn
};
}
});

return mappedData;
}

Important Notes​

Version Notice

The metadata properties endpoint is largely up-to-date but may not reflect the absolute latest additions. Always test with actual API responses to confirm available fields.

Best Practices
  • Use this endpoint to understand available fields before implementing your integration
  • Cache the response locally as the schema doesn't change frequently
  • Not all properties will be present in every verification flow - availability depends on:
    • Selected check types in the flow configuration
    • User-provided data
    • Third-party service availability
    • Verification success