Entities and q_ids - Quoin Data

Every real-world thing the API knows about is an entity with a permanent q_id: a type prefix followed by a UUID, for example addr_01a12e0d-2ece-77ad-b5b0-430ab9658f29. Store q_ids; they do not change between data refreshes.

Prefix	Entity	Accepted as input
`addr_`	Address	Yes
`parc_`	Parcel	Yes
`acct_`	Tax account	Yes
`unit_`	Unit	Yes
`juri_`	Jurisdiction (state or county)	No. Returned in results only
`rec_`	One source record. All its versions share the id	Use with `history`

Entities by state

Each state’s model follows what its publishers name, so not every entity type exists everywhere.

State	Entities	Links
Washington, D.C.	address, parcel, tax account, unit	parcel `at` address, unit `at` address, account `billed_to` parcel, parcel `in` jurisdiction
Maryland	address, tax account	account `at` address, account `in` jurisdiction
Virginia	address, parcel	parcel `at` address, parcel `in` jurisdiction

Counties are part_of their state.

Links

connected walks these links up to three steps out. Each result says how it was reached:

{
  "q_id": "acct_8f216956-ff98-4f4c-ba8f-6d8efc0ac929",
  "type": "acct",
  "relation": "billed_to",
  "via": "parc_96624cd7-de8b-4592-a17d-dd44049fb1ed",
  "depth": 2
}

Relation	Meaning
`at`	A parcel, unit or account is at an address
`billed_to`	A tax account bills a parcel
`in`	An entity is in a jurisdiction
`part_of`	A county is part of its state

Jurisdictions appear in results but are not expanded, and you cannot pass a juri_ id as input.