IH
At Irembo, Service Builders connect government services to partner systems every week. In this course we connect a brand-new partner, KEZA (a fictional national skills-training agency), to the Irembo service “Apply for KEZA Digital Skills Training”, step by step, and you build the same integration yourself.
Every endpoint and every mock you will see is real: it exists on staging with a VICTOR_ name (the course’s reference objects), and every response shown was captured from staging on 26 and 28 Sep 2026.
How the engine thinks
Put data where the partner wants it
Every auth type KEZA could ask for
Make answers useful and safe
Real-world payloads
Run it in production
Prove it
By the end you can take any partner’s API documentation and deliver a working, tested and operable IremboHub integration using only the Integration Management Portal and curl: design it, mock the partner, configure the endpoint and its authentication, prove it end to end, and support it in production.
From Module 2 on, every lesson follows the same six steps, so you only have to think about one new idea at a time.
What the Irembo service needs and why.
The slice of the KEZA API you must call.
The mock that simulates KEZA in Mocks, rule by rule.
The exact portal fields and the JSONata mapping, line by line.
The curl to /fetch/sync or /push/sync and the real staging output.
What to notice, the gotchas, a quick check, and a small task you do yourself.
Adults learn fastest from a realistic problem, a worked example, then practice with less help each time. Each lesson shows one worked example (how your teacher does it, on the reference VICTOR_ objects), then ends with a Your turn task you do without the answer; the capstone in Module 7 is fully independent.
No staging access yet? You can still complete the course: every output is shown exactly as staging returned it.
Your tech notes · Use your own first name as a prefix
When you practise, never edit the reference
VICTOR_objects. Create your own, prefixed with your first name. In every Your turn task you will see variables such as${YOUR_FIRST_NAME}_KEZA_ELIGIBILITY_FETCH(codes, upper case) and/${your_first_name}/keza/v1/eligibility(paths, lower case). Replace the variable before you save: for Aline that givesALINE_KEZA_ELIGIBILITY_FETCHand/aline/keza/v1/eligibility. The portal rejects$in URLs, and a code is permanent. Two active mocks with the same method, path and conditions are rejected, so the prefix also keeps you from colliding with classmates.