This API documentation includes the endpoints that can be consumed by UFone Pakistan. The API exposes 4 endpoints.
4 endpointsThis integration provides endpoints to check subscriber eligibility and to add advances for subscribers on the AV advance system</br>. The API exposes 2 endpoints.
2 endpointsFinance m/s for processing and tracking lending of Airtime, MoMo, and Data <style> table { border: 2px solid powderblue; } </style> <h2>Release Notes</h2> <table> <th>Version</th><th>Detail</th> <tr><td>5.0.149</td><td>Logging issues fixed when logging all even though set to error.</td></tr> <tr><td>5.0.132</td><td>Deprecated queued advance state (statusId=6)<br><b><font color = red>DevOps, this r. The API exposes 23 endpoints.
23 endpoints**Release Notes** |Version| Detail| |---|---| |5.0.21 |Logging issues fixed when logging all even though set to error. | |5.0.12 |Addition of UI endpoints. | |5.0.9 |Upgraded to Java 17. | |4.0.8 |Upgraded to Java 11 and containerised. Added /authorize endpoint. | **Introduction** This microservice acts as a central gatekeeper for calls coming in from a variety of channels. This microservice is us. The API exposes 9 endpoints.
9 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.