Get Collection Wallet Statement

Use this endpoint to retrieve the statement of your collection wallet.

Endpoint

POST /wallet/collection-statement

Request

Headers

• Content-Type* — Must be application/json

• x-account-id* — Your unique TemboPlus account identifier

• x-secret-key* — Your TemboPlus API secret key

• x-request-id* — Unique UUID per request for tracing

Body Parameters

• startDate* (string) — The starting date of the statement period, formatted as YYYY-MM-DD.

• endDate* (string) — The ending date of the statement period, formatted as YYYY-MM-DD.

Example Request Payload

{
  "startDate": "2025-09-01",
  "endDate": "2025-09-30"
}

Responses

200 OK

Returns the current and available balance along with account details such as account name, number and status.

Response Format

[
  {
    "tranRefNo": "sample-collection", // Your original transaction reference
    "valueDate": "2025-09-12 15:25:35", // Date when transaction was processed
    "txnDate": "2025-08-25 00:00:00", // Original transaction date
    "narration": "Inbound trx from 255628212684", // Transaction description
    "debitOrCredit": "CR", // Transaction type (CR = Credit, DR = Debit)
    "amountCredited": 1000, // Amount credited to your account (TZS)
    "amountDebited": 0, // Amount debited from your account (TZS)
    "balance": 8880 // Account balance after this transaction (TZS)
  },
  {
    "tranRefNo": "sample-collection-PAYIN", // Service fee transaction reference
    "valueDate": "2025-09-12 15:25:36", // Date when fee was processed
    "txnDate": "2025-09-12 00:00:00", // Fee transaction date
    "narration": "SERVICE FEE FOR REF:sample-collection TXNID:ZYIcRFnHFkXz Inbound trx from 255628212684", // Service fee description
    "debitOrCredit": "DR", // Transaction type (DR = Debit for fees)
    "amountCredited": 0, // Amount credited (0 for fee transactions)
    "amountDebited": 15, // Service fee amount debited (TZS)
    "balance": 8865 // Account balance after fee deduction (TZS)
  }
]

400 BAD REQUEST

Returned when the request payload is missing one or more required fields, or when any field contains invalid data.

Response Format

{
    "statusCode": 400,
    "reason": "VALIDATION_ERROR",
    "details": {
        "endDate": "\"endDate\" is required"
    },
    "message": "{\"endDate\":\"\\\"endDate\\\" is required\"}"
}

Fields inside details and message are optional and vary depending on the specific validation failure.

---

Common Validation Errors to Avoid

• Ensure all required fields are included in the request body in the right format.

• x-request-id must be included in the request headers.

401 UNAUTHORIZED

Returned when authentication headers are missing or invalid.

Response Format:

{
    "statusCode": 401,
    "reason": "INVALID_CREDENTIALS",
    "details": {}
}

500 INTERNAL SERVER ERROR

Indicates a temporary issue within TemboPlus. Retry later or contact TemboPlus Support with your x-request-id.

Response Format:

{
    "statusCode": 500,
    "reason": "SERVER_ERROR"
}