Back to Blog
Developer

API Design Principles We Follow at Bitako

February 10, 20265 min read

Consistency Over Cleverness

Every endpoint in the Bitako API follows the same patterns. Request bodies always use camelCase. Timestamps are always ISO 8601. Amount fields are always in the smallest currency unit (kobo for NGN).

Idempotency Is Non-Negotiable

Every state-mutating endpoint (POST, PATCH) requires an `Idempotency-Key` header. This protects against duplicate operations caused by network retries.

Error Messages That Actually Help

We put significant effort into error messages. Instead of `400 Bad Request`, you get: ```json { "error": "validation_error", "message": "amount must be a positive integer in kobo", "field": "amount" } ```

Pagination That Makes Sense

All list endpoints return cursor-based pagination. Cursor pagination is consistent regardless of data mutation between requests — unlike offset pagination which can skip or duplicate items.