For App Developers

UUPG+ Lists

The UUPG+ Global Engagement Alliance maintains four nested cohorts of People-Group-in-Country (PGIC) records. Global.Church publishes the first three as saved-query routes so Alliance members can fetch them with a single HTTP GET — no SPARQL string to maintain. The fourth (Hotspot Lists) is curator-submitted and scaffolds when a partner publishes.

All routes return SPARQL results in application/sparql-results+json by default. Set the Accept header to text/csv for spreadsheet-friendly output, or application/sparql-results+xml for XML.

Quick reference

Endpoint	Returns	~Live count
GET /v0/uupg/base-list	All known PGICs from JP + IMB, deduped by (ROP3, ROG3)	19,131
GET /v0/uupg/watch-list/jp	JP arm of the Watch List (≤2% Evangelical or <75 believers)	7,744
GET /v0/uupg/watch-list/imb	IMB arm of the Watch List (GSEC 0–2)	7,092
GET /v0/uupg/watch-list/combined	JP ∪ IMB deduped by (ROP3, ROG3)	11,993
GET /v0/uupg/watch-list/ongoing	Phase 5/6 removal candidates	0 today
GET /v0/uupg/list	Watch List minus recent church-planting engagement	11,993 today

Counts as of mid-May 2026. Live counts vary with new data ingest; query the endpoint for current numbers.

The four lists

The Alliance defines a nested hierarchy. Each list is a subset of the one above it.

1. Base List — every PGIC reported by any member source. The widest possible roster of "people groups, by country, that anyone has documented." JP and IMB both contribute; Accelerate and Etnopedia integration is on the roadmap.
2. Watch List — PGICs that look unreached / un-self-engaged on initial inspection. Two arms: the JP arm (numeric Evangelical thresholds) and the IMB arm (GSEC 0–2). The combined route returns the union, deduplicated.
3. UUPG List — Watch List minus PGICs with a recent (≤ 2 years old) active engagement attestation indicating church-planting work. Today these subtraction triples are sparse, so the UUPG List equals the Combined Watch List in count; this resolves as Alliance members file MVE-Report attestations.
4. Hotspot Lists — country/region-scoped sub-lists curated by Alliance partners through in-country round-tables. Not exposed as a saved-query route yet; lives at https://data.global.church/hotspots/{ROG3}/ once a partner publishes.

The ongoing-method Watch List is a separate query that flags PGICs whose current Phase-of-Engagement (Phase 5 or 6) has crossed the spec's population-banded Evangelical-Christian floor — these are removal candidates. Returns zero rows today because no PoE-methodology assessments link to Phase 5/6 PGICs yet.

Example: fetch the UUPG List

Code
 
curl -H "X-Api-Key: $GC_API_KEY" \
     -H "Accept: application/sparql-results+json" \
     https://api.global.church/v0/uupg/list

The response is standard SPARQL 1.1 Results JSON:

Code
 
{
  "head": { "vars": ["rop3Concept", "rog3Concept", "pgName", "watchSources"] },
  "results": {
    "bindings": [
      {
        "rop3Concept": { "type": "uri", "value": "https://data.global.church/his/rop3/100161" },
        "rog3Concept": { "type": "uri", "value": "https://data.global.church/his/rog3/NER" },
        "pgName":      { "type": "literal", "value": "Tuareg, Air" },
        "watchSources": { "type": "literal", "value": "JP,IMB" }
      }
    ]
  }
}

Example: CSV download

Code
 
curl -H "X-Api-Key: $GC_API_KEY" \
     -H "Accept: text/csv" \
     https://api.global.church/v0/uupg/list \
     -o uupg-list-$(date +%F).csv

Per-country filtering

The saved-query routes return the global list. For country-scoped subsets, post a wrapper query against the raw /v0/sparql endpoint adding FILTER(?rog3Concept = <https://data.global.church/his/rog3/IND>). See the SPARQL Quickstart for the general pattern. A future enhancement may add per-country saved-query variants (/v0/uupg/list/{rog3}) if demand warrants it.

Where the counts come from

The route handlers POST hardcoded SPARQL templates against the live gc-core triplestore. The canonical query bodies live in the open-source core repo as uupg-*.rq — read them if you want to audit the exact computation. Each handler is a thin proxy; no caching layer sits between the route and GraphDB, so the count is whatever the graph currently holds.

What's not yet here

• Hotspot Lists — sub-national curator submissions naming specific people-group / sub-region pairs as priorities. Ships when an Alliance partner is ready to publish.
• MVE-Report attestation richness — finer-grained engagement attestation fields (claimed phase, claimed number of churches, claimed number of believers, claimed reporter name) that MVE-Report submissions can carry. Ships alongside the first MVE submitter integration.
• Per-country saved-query variants — convenience surface; the global lists already accept country-scoped post-filtering via the raw /v0/sparql endpoint.