Authentication & Conventions
Every request to the EFRIS API is authenticated with your business's API key, sent as a Bearer token. You can generate and rotate the key from your EFRIS Simplified dashboard under Security.
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
| Environment | API key | Use for |
|---|---|---|
| Production | live_... |
Live traffic - every request fiscalises against URA for real. Available once your business has been moved to live |
| Sandbox | test_... |
Building & testing your integration - reaches URA's sandbox, not their live system |
Both environments share one base URL, https://app.efrissimplified.com/api/efris/{tin}. The API
key you send decides which one a request goes to.
test_ key first, which talks to URA's separate testing environment, then swap in your
live_ key when you're ready to go live. Your sandbox key keeps working after that, so you can
keep testing changes against it.
{tin} is the TIN of the business registered on EFRIS Simplified. All endpoints are
POST and accept/return JSON.
Pricing rule: amounts are tax-inclusive
All invoice amounts are gross (tax-inclusive). If an item's net price is 10,000 UGX and VAT is 18%, you send a unit price of 11,800 UGX. The VAT portion is then reported per line and per tax category - see E-Invoices for worked examples. A business not registered for VAT sends no tax at all - see E-Receipts.
Security recommendations
- Store the API key server-side. Never embed it in mobile apps, browser JavaScript, or public repositories.
- Rotate the key from your dashboard if you suspect it has leaked - the old key stops working immediately.
- Always call the API over HTTPS; plain HTTP requests are not served.
Sign in to the dashboard · Get started