v1

latestOpenAPI 3.1.02026-07-2210284274.4 KB
Property Catalog

Resolve identifiers to property_rids (and contribute them)

The primary fact-contribution path. Takes identifiers plus a provenance envelope and returns stable property_rids. In resolve mode (default) it auto-creates missing catalog entries and logs demand activity — so resolving your own identifier list IS the contribution. property_rid is a non-authoritative join/match handle, never an authorization credential. Re-resolving is idempotent on the identifier→rid mapping but additive on the activity log.

post/api/registry/resolve

Request body

mode'resolve' | 'lookup'

resolve (default) contributes the identifiers, auto-creates missing catalog entries, logs demand activity, and returns rids — requires authentication. lookup is a pure read: no write, no activity log, no auth.

Example request

{
  "identifiers": [
    {
      "type": "domain",
      "value": "nytimes.com"
    }
  ],
  "provenance": {
    "context": "unilever_q3"
  }
}

Response

Resolve/lookup result

server_timestampstring required

Example response

{
  "resolved": [
    {
      "identifier": {
        "type": "domain",
        "value": "nytimes.com"
      },
      "classification": "property"
    }
  ]
}