FLfloqer
ackDB

List Observe person fields

The field catalog for the PERSON grain (#329) - one row per human, spanning every company they have been at. Structurally different from the other two grains: a person holds durable KEYS and EVENTS, never traits, so the catalog ships NO trait descriptors (a trait filter is a 400). What it does ship: system columns (name, affiliation_count, last_active, is_internal, key_count, status, created_at, updated_at, plus the projection-only companies and activity columns), durable-key columns (idl__<type> - linkedin_url, email_address, person-scoped product ids), promoted event-metadata columns (emf__…, #212) and per-event-type count columns (evc__…, #322) - both correlated on the person's OWN timeline (entity_events.person_id), so they span every company the human has worked at. One field is deliberately NOT here: the company filter entity_id (#334). A human has 1..N companies, so it is a predicate (an EXISTS over their active edges), never a column - and a catalog entry would let a UI offer it as one and 400 the view. It is documented on POST /observe/persons/query, and the company grain's filter-only source_present is withheld from that grain's catalog for the same reason.

get/api/v1/ackdb/observe/persons/fields

Request

  • Base URL
    http://localhost:3009
  • Auth
    HTTP bearer

Response

The field catalog (may be coverage-ordered).

Example response

{
  "data": [
    {
      "key": "event_count",
      "label": "Event Count",
      "source": "system",
      "coverage": 1280,
      "sortable": true,
      "filterable": true,
      "distinctValuesUrl": "/observe/companies/fields/hubspot_lifecycle_stage/values"
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.