Home API Documentation
Developer Documentation - Overview

One REST API to make any system EFRIS-compliant.

The EFRIS Simplified API lets any ERP, POS, or custom business system connect to URA EFRIS in Uganda over plain JSON. This page is a public overview of what the API covers. The complete field-level reference is shared directly with developers once their business is set up on the platform.

How it works

URA's EFRIS protocol is complex enough that teams routinely spend months building and maintaining a direct integration. EFRIS Simplified removes that burden: your system sends a simple JSON request over HTTPS, and the API hands back everything your invoice needs - the Fiscal Document Number (FDN), verification code, and QR code - ready to print or store.

Environment Purpose
Production Live traffic - every request fiscalises against URA for real.
Sandbox A separate environment for building and testing your integration against URA's sandbox, not the live system.

Every endpoint is a POST request that accepts and returns JSON, authenticated with a Bearer API key generated from your EFRIS Simplified dashboard. Requests and responses follow a simple, predictable structure across the whole API - no protocol-level work required on your side.

No specialist EFRIS knowledge needed. Your developers only need to work with a standard JSON API and a Bearer API key - in any programming language that can make an HTTPS request.

What the API covers

Eight documentation sections spanning the full EFRIS lifecycle - from authentication to reference data. The full reference includes request/response field definitions, validation rules, and worked examples for each.

Authentication & Conventions

How to authenticate your requests and the conventions every endpoint follows.

Goods Registration

Register the goods and services you sell with URA - standard goods, packaged items, excise-rated products, and services.

POST /register-good-or-service

Stock Management

Keep URA's inventory ledger in sync with yours - stock increases, decreases, and branch-to-branch transfers.

POST /stock-management POST /transfer-stock + 7 record queries

E-Invoices

VAT-registered businesses fiscalise sales and receive the FDN, verification code, and QR code - standard, export, excise, and industry-specific invoices.

POST /issue-e-invoice POST /issue-e-invoice/batch

E-Receipts

Businesses not registered for VAT fiscalise sales as receipts with no tax lines, and receive the same FDN, verification code, and QR code.

POST /issue-e-receipt POST /issue-e-receipt/batch

Credit Notes

Reverse or adjust fiscalised invoices when goods are returned, and track approval status.

POST /apply-for-credit-note POST /query-invoice-remain-details + 6 more

Data Lookups

Reference data for building your integration - TIN validation, exchange rates, commodity categories, excise codes, and branches.

POST /validate-tin POST /query-hs-codes + 11 more

Exports & High Sea / Bond

HS codes, the customs status of export invoices, and the references behind High Sea and Bond sales.

POST /query-export-invoice-status POST /query-high-sea-bond-details + 1 more

Deemed & Exempt Projects

Register deemed VAT and exempt projects with URA and invoice against them once approved.

POST /apply-deemed-exempt-project POST /apply-deemed-vat-exemption

Buyers, Agents & Accounts

Saved buyers, buyer corrections, invoicing as an agent, USSD accounts and EFRIS password resets.

POST /manage-frequent-contact POST /query-agent-relations + 5 more

Fuel Stations (EDC)

The full fuel station cycle - pumps, nozzles and tanks, fuel sales, nozzle status, shifts and EDC invoices.

POST /upload-shift POST /query-edc-invoices + 8 more

Invoice Response Structure

Where the FDN, verification code, and QR code live in a fiscalisation response, and how to print a compliant e-invoice.

Best Practices

The rules that keep an integration reliable and tax reporting accurate over time.

Built for any language, any system

If your system can make an HTTPS POST request, it can fiscalise invoices through EFRIS Simplified - custom-built ERPs, point-of-sale systems, e-commerce platforms, school and hospital management systems, accounting software, and mobile apps, in PHP, Java, C#, Python, Node.js, Dart, Go, or anything else.

  • No specialist EFRIS knowledge required: the technical complexity of URA's protocol is handled for you.
  • Simple, predictable JSON: no protocol-level work required on your side.
  • Clear validation: helpful error responses before anything reaches URA.
  • A sandbox environment: build and test safely before switching to production.

Frequently asked questions

Do I need specialist EFRIS knowledge to integrate?

No. URA's technical requirements are handled entirely by EFRIS Simplified. Your system only ever sends and receives plain JSON, using a standard Bearer API key.

Which systems can integrate with the API?

Any system that can make an HTTPS POST request: custom ERPs, POS systems, e-commerce platforms, school and hospital management systems, accounting packages, and mobile apps - in any programming language.

Is this the official URA documentation?

No - this documents the EFRIS Simplified middleware API. Field names, codes, and validation rules intentionally mirror URA's official EFRIS interface specification, so knowledge transfers both ways, but you never talk to URA's servers directly.

Where can I find the full API reference?

This page is a public overview. The complete reference - request and response field definitions, validation rules, and worked examples for every endpoint - is shared directly with developers who reach out to us, once their business is set up on EFRIS Simplified.

Building an integration? Get the full reference.

Talk to us about your system, get set up on EFRIS Simplified, and we'll hand your developers the complete API reference - every field, every validation rule, every example - to build against.