Developer integration boundaries
Understand what can be integrated today and what is not a supported public API.
On this page
Current integration contract
DeniFlow currently exposes application endpoints for its own authenticated web interface. There is no published customer API-key system, stable public API contract, SDK or customer webhook subscription. Internal endpoints should not be used as an external integration contract.
Supported exchange today
Use permissioned CSV imports and audited exports. Customer CSV imports add customer records only. Bank and M-Pesa statement imports add reconciliation evidence only. They do not create money movements, allocate receipts or verify provider settlement.
Request an integration
Contact DeniFlow with the system name, direction of transfer, required fields, frequency and who authorizes access. Agree on a supported contract before implementation. Do not share a staff password, copy browser session cookies into a script or place secret keys in frontend code.
Provider capabilities
Resend is used for configured email delivery. WhatsApp opens a reviewed manual draft outside DeniFlow. M-Pesa references and CSV statements support review, but the complete live Daraja settlement-confirmation workflow is not available. SMS, bank feeds, accounting sync, inbound WhatsApp and eTIMS are not enabled.
Need help with this workflow?
Ask through account support