Daon · Schema

DocumentNumberTrendRecordDto

Trend record for document number occurrences

CompanyDigital IdentityIdentity VerificationAuthenticationBiometricsFraud PreventionMulti-Factor AuthenticationFIDO

Properties

Name Type Description
id string Unique identifier for the trend record
type string Type of the trend record (determines which specific fields are available)
recordedDtm string Timestamp when the occurrence was recorded (generated on storage)
processInfo object Process information associated with this trend record
trendGroup string Optional trend group for grouping trends by business context
expiresAfter string The calculated expiration timestamp (recordedDtm + expiresAfterDays)
expiresAfterDays integer The number of days after which the record will expire
attributes object Optional additional attributes for the trend record
value string The value of the identifier being recorded
documentType string The document type (e.g., 'Austria - Id Card (2021)', 'Serbia - Id Card (2009-2014) #1')
View JSON Schema on GitHub

JSON Schema

daon-document-number-trend-record-dto-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/daon/json-schema/daon-document-number-trend-record-dto-schema.json",
  "title": "DocumentNumberTrendRecordDto",
  "description": "Trend record for document number occurrences",
  "x-generated": "2026-11-10",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/daon-trends-api-openapi.yml#/components/schemas/DocumentNumberTrendRecordDto",
  "allOf": [
    {
      "$ref": "#/$defs/AbstractTrendRecordDto"
    },
    {
      "type": "object",
      "properties": {
        "value": {
          "type": "string",
          "description": "The value of the identifier being recorded",
          "maxLength": 100,
          "minLength": 0
        },
        "documentType": {
          "type": "string",
          "description": "The document type (e.g., 'Austria - Id Card (2021)', 'Serbia - Id Card (2009-2014) #1')",
          "maxLength": 250,
          "minLength": 0
        }
      }
    }
  ],
  "required": [
    "processInfo",
    "type",
    "value"
  ],
  "$defs": {
    "AbstractTrendRecordDto": {
      "type": "object",
      "description": "Base class for trend records with common metadata fields",
      "properties": {
        "id": {
          "type": "string",
          "description": "Unique identifier for the trend record",
          "readOnly": true
        },
        "type": {
          "type": "string",
          "description": "Type of the trend record (determines which specific fields are available)",
          "minLength": 1
        },
        "recordedDtm": {
          "type": "string",
          "format": "date-time",
          "description": "Timestamp when the occurrence was recorded (generated on storage)",
          "readOnly": true
        },
        "processInfo": {
          "$ref": "#/$defs/ProcessInfoDto",
          "description": "Process information associated with this trend record"
        },
        "trendGroup": {
          "type": "string",
          "description": "Optional trend group for grouping trends by business context",
          "maxLength": 32,
          "minLength": 0,
          "pattern": "^[a-zA-Z0-9_]+$"
        },
        "expiresAfter": {
          "type": "string",
          "format": "date-time",
          "description": "The calculated expiration timestamp (recordedDtm + expiresAfterDays)",
          "readOnly": true
        },
        "expiresAfterDays": {
          "type": "integer",
          "format": "int32",
          "description": "The number of days after which the record will expire",
          "minimum": 1
        },
        "attributes": {
          "type": "object",
          "additionalProperties": {},
          "description": "Optional additional attributes for the trend record"
        },
        "value": {
          "type": "string"
        }
      },
      "required": [
        "processInfo",
        "type"
      ]
    },
    "ProcessInfoDto": {
      "type": "object",
      "description": "Process information associated with a watchlist entry or trend record",
      "properties": {
        "processDefnId": {
          "type": "string",
          "description": "Unique identifier for the process definition",
          "maxLength": 26,
          "minLength": 26
        },
        "processDefnName": {
          "type": "string",
          "description": "Human-readable name of the process definition",
          "maxLength": 50,
          "minLength": 0
        },
        "processDefnVersion": {
          "type": "integer",
          "format": "int32",
          "description": "Version number of the process definition",
          "minimum": 1
        },
        "processInstanceId": {
          "type": "string",
          "description": "Unique identifier for the process instance",
          "maxLength": 26,
          "minLength": 26
        }
      },
      "required": [
        "processDefnId",
        "processDefnName",
        "processDefnVersion",
        "processInstanceId"
      ]
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/daon-document-number-trend-record-dto"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.