Developers

An API that posts into balanced books

The same REST API that powers the field app, for your own applications and partners.

The same API that powers the Zenus field app is available to your own applications. It covers customer search, balance and ledger enquiry, field deposit and withdrawal batches, multi-credit and multi-debit batches, journal entries, expense and loan approvals and reference lookups.

Every mutating call accepts an Idempotency-Key header and replays the original response on retry; a same-day duplicate is bounced with a 409 until confirmed; and every approval enforces maker-checker with a 403. Tokens are revoked the moment a staff member is deactivated.

Endpoint groups

Bearer-token authentication with per-user rate limits
Customer search, balance and ledger endpoints
Field deposit, field withdrawal and transfer batch endpoints
Journal, expense and loan approval endpoints
Idempotency-Key header with cached replay
Duplicate detection with explicit confirmation
Maker-checker enforced on every approve/reject
Instant token revocation on deactivation

POST /api/v1/admin/field-deposits

curl -X POST https://api.example/api/v1/admin/field-deposits \
  -H "Authorization: Bearer <token>" \
  -H "Idempotency-Key: 8f3c2a1e-..." \
  -H "Content-Type: application/json" \
  -d '{
    "cash_account_id": 3,
    "value_date": "2026-09-14",
    "lines": [
      {"account_number": "1001000123", "amount": 15000},
      {"account_number": "1001000456", "amount": 5000}
    ]
  }'

# 201 Created  → batch awaiting approval
# 409 Conflict → duplicate_detected: resend with confirm=true
# 403          → approver cannot be the maker

Illustrative request. Endpoints, fields and limits are documented for API customers.

Building on Zenus?

Tell us what you are integrating and we will set up API access on a sandbox institution.

Request API access Integrations

Prefer WhatsApp? Chat with us