How to use this site
If you're new here, learn how to navigate these DigiTax Zimbabwe API Hub pages below
📖 Guides
This is the overview page of the Guides section.
Explore the guides as outlined on the left-hand menu.
Guide page features
-
Table of contents on the right-hand side (Desktop)
-
Hover to view Glossary definitions (mouseover): Acronyms and technical terms listed in the Glossary appear on a page underlined with a dotted line.
Like API, hover (or tap on mobile) to view the definition.
🚦 Interactive API Docs
For a great developer experience, the endpoints in the DigiTax Zimbabwe API reference are interactive.
Once you're set up in the DigiTax Dashboard, you can generate a sandbox or LIVE X-API-Key for authorization. Read more on the API prerequisites.
Explore the API endpoints.
Code samples
You can make use of code samples in over 20 programming languages for requests to get you started quickly.

Pagination
We support cursor-based pagination requests for endpoints whose GET requests return a list of objects.
Parameters for paginated requests
The following are optional query parameters for paginated requests like GET receipts.
| Parameter | Explanation |
|---|---|
before | A cursor pointer to an ID before which we want results (for previous page) |
after | A cursor pointer to an ID after which we want results (for next page) |
page_size | The maximum number of items to return per page (defaults to 20, maximum: 20) |
Pass at most one of before and after. Sending both returns 400 Bad Request. Each response's pagination object gives the next and previous cursors to pass back.
These are also explained on the API endpoint page(s).
Parameters
Parameters come in three types in the DigiTax Zimbabwe API:
- Path Params: Identifiers in the URL, like the receipt ID in GET receipts/{receipt_id}
- Query Params: Used in listing endpoints like GET receipts, for example
status,fiscal_day_idorreceipt_date_from - Body Params: Passed in JSON request bodies like POST items or POST receipts
Amounts and quantities
Amounts on receipts are whole numbers of cents (price_cents, total_cents, amount_cents): 150 is 1.50. Quantities are whole numbers of thousandths (quantity_milli): 1500 is 1.5. Items are the exception: an item's default_price is in major units, for example 1.50.
Times
Every time the API returns, and every time in a callback, is RFC 3339 in Central Africa Time (CAT, Africa/Harare, UTC+02:00, no daylight saving), for example 2026-11-13T09:48:02+02:00. Read the offset rather than treating the time as UTC.
Time filters such as receipt_date_from take RFC 3339 with any offset. A time without an offset is refused with 400. In a query string, encode the + of +02:00 as %2B:
GET /receipts?receipt_date_from=2026-07-14T00:00:00%2B02:00💬 We're here to help
If you get stuck, email us or use the DigiTax chat on the bottom right of any page.
We're excited you're here! 💚
Updated about 2 hours ago