NIC IMIS Partner API Documentation
Programmatic access to the National Insurance Corporation of Tanzania's underwriting platform. Two REST surfaces — pick the one that fits your integration scope. Both share the same authentication model and callback contract.
General Public Open API
REST API for third-party partners to place proposals against the full IMIS product catalogue — motor, marine, fire, engineering, life and every other approved product. Product-class filter tags let partners scope which slice of the catalogue they consume.
- One credential pair → every non-rider product
- `?filter_tag=` narrows results by product class
- Callback-driven lifecycle (control number → payment → TIRA → commencement)
http://imisuat.nicinsurance.co.tz/uat/mware/general/v1
A single Markdown context file describing the full integration contract for this API — base URL, auth, endpoints, request/response schemas, callback kinds, error codes, retry patterns, and a prompt-ready snippet. Paste it into Claude, Copilot, Cursor or any AI coding tool and ask it to build your client.
Marine Insurance API
REST API tuned to the Marine line of business. Same callback / lifecycle contract as the General API, scoped to marine products only. Preserved as a dedicated surface so existing marine integrations keep working unchanged.
- Scoped to marine cargo, hull and machinery products
- Six callback channels (control number, approval, payment, TIRA, commencement)
- Same header contract as the General API
http://imisuat.nicinsurance.co.tz/uat/mware/marine/v1
A single Markdown context file describing the full integration contract for this API — base URL, auth, endpoints, request/response schemas, callback kinds, error codes, retry patterns, and a prompt-ready snippet. Paste it into Claude, Copilot, Cursor or any AI coding tool and ask it to build your client.
Getting credentials
API keys are issued by NIC operations against a scoped integration record. Reach out with the intended use, the API surface you need (Marine, General Public Open, or both), and — for the General API — the product-class filter tags you require. Ops will provision a credential pair, hand you the plaintext exactly once, and lock the integration to that scope.