When a reviewer finishes the endorsement geo filter (EndorsementFragment -> EndorsementViewModel.getFarmersGeoWise), the app loads farmers for that habitation / VO / village. The live path clears ie_flat_entity and inserts these rows (insertFlatSchemDataForVoids), so the endorsement lists show only that geography. An unused repository variant builds the same request through CoreAPI. Errors show an error state and leave the local table unchanged.
Headers
Header
Value
Notes
X-SESSIONID
<session token>
Not set by the call site. AuthInterceptor (OkHttpClientInterceptor) adds it from AndroidSessionManager. On a 401 or 400 it invalidates the token, gets a fresh one and retries once.
Parameters
Param
In
Required
Example
Notes
name
query
Yes
PlusOneWorkNodeFarmerListGeoWiseNoPagination
Dataset name. The rtld executor (/rtld/api/dataset/v1/execute) picks the dataset by this query param.
version
query
Yes
1
Dataset version. Always 1.
format
query
Yes
json
Response format. Always json, so the body is a JSON array of row objects.
Dataset input parameters as KEY=value pairs joined with "--". Aliases are wrapped in single quotes. WORK_NODE_HABITATION_ALIAS / WORK_NODE_VO_ALIAS / WORK_NODE_VILLAGE_ALIAS = selected geography; OFFSET_VALUE=0 and LIMIT_VALUE=10 are hard-coded (the dataset name says no pagination, so the server presumably ignores them). Note: the live code calls this on the rtld executor (GET /rtld/api/dataset/v1/execute?name=...), not the commons-report-service path in the key.
Request
No body. habitation / VO / village alias, offset, limit