Amanzi API
Leakages, complaints, new connection applications, response times, locations, and resolution status.
CollectTech Developers
Build secure integrations for water utility operations.
Use CollectTech APIs to exchange approved utility data across MAJIIS, Amanzi, Makusanyo, CT GIS Field, and CT Fundi. Access is governed at utility level, with sandbox testing before production keys are issued.
Utility Integration Console
Sandbox ready
Amanzi
GIS
Revenue
Field
Scopes
Approved utility endpoint
GET /api/v1/amanzi/leakages
{
"utility_id": "mwauwasa",
"scope": "amanzi.leakages.read",
"status": "authorized",
"filters": ["date", "status", "operational_area"],
"format": "json"
}
Access model
Utility scoped
Map format
GeoJSON
Mode
Sandbox first
API products
One developer program for the full water utility workflow.
The first API releases should focus on approved data exchange, controlled dashboards, GIS visibility, and operational records that help utilities and government teams make better decisions.
Makusanyo API
Customer visits, debt records, collections, reconnections, disconnections, and field outcomes.
GIS API
Customers, operational areas, valves, tanks, bulk meters, pipes, mapped coverage, and GeoJSON exports.
CT Fundi API
Technician tasks, repairs, materials, installation work, photos, and real-time field activity summaries.
Oversight API
EWURA indicators, Ministry dashboards, utility performance, water rationing, and policy reporting metrics.
Governance
Production access is approved per utility.
CollectTech integrations are designed around utility-level authorization. A Ministry or partner integration can only access a utility after the relevant approval, scope, and environment have been recorded.
Sandbox before production
Developers test with synthetic or anonymized data before production credentials are issued.
Scoped API keys
Keys are limited by utility, environment, data domain, and read or write permissions.
Audit-ready exchange
Requests are logged with client, utility, endpoint, status, source IP, and timestamp.
1
Request access
Submit organization details, intended use, utility scope, and technical contact.
2
Review data agreement
Confirm the utility approvals, MAJIIS relationship, eGA expectations, and allowed data domains.
3
Test in sandbox
Validate authentication, filters, GeoJSON, pagination, webhooks, and sample datasets.
4
Issue production keys
Production credentials are issued only after approval, security checks, and scope confirmation.
Request developer access.
Tell us what you want to integrate. This request does not create a production API key automatically. The CollectTech team will review the organization, utilities, data scope, and environment before access is granted.
Ask for sandbox access to test API workflows.
Request production access for approved utility-level data exchange.
Share GIS, operational, revenue, field, and oversight integration needs.