canonical: https://jentic.com/apis/swaggerhub.airvantage-team/avmicroservicefinance

# Airvantage Team av_microservice_finance

Finance 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.

## For AI agents

Programmatically creates and registers a subscriber advance., adds an advance repayment.. Covers 23 operations.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Creates and registers a subscriber advance.
- Adds an advance repayment.
- Returns a list of msisdns based on advance details.
- Get entity type balance for a subscriber.
- Deactivates this subscsriber.  Future references to this MSISDN will create a ne

## Use cases

### Analytics Operations

Use the av_microservice_finance to perform analytics operations programmatically. The API provides 23 endpoints covering core functionality including creates and registers a subscriber advance., adds an advance repayment., adds a charge against the specified advance..

Example prompt: Call GET /addAdvance to creates and registers a subscriber advance.

### Automated Public Management

Automate public operations by combining multiple av_microservice_finance endpoints. Agents can adds an advance repayment. and then adds a charge against the specified advance. in a single workflow.

Example prompt: Call GET /addRepayment to adds an advance repayment., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call av_microservice_finance endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'creates and registers a subscriber advance.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /addAdvance | Creates and registers a subscriber advance. |
| GET | /addRepayment | Adds an advance repayment. |
| GET | /addCharge | Adds a charge against the specified advance. |
| GET | /addSubscriber | Adds a subscriber to the Lending schema. |
| GET | /getMsisdnList | Returns a list of msisdns based on advance details. |
| GET | /getBalanceEntity | Get entity type balance for a subscriber. |
| GET | /churnSubscriber | Deactivates this subscsriber. Future references to this MSISDN will create a ne |
| GET | /doMSISDNSwap | Changes MSISDN whilst retaining subscriber history. |

## Key resources

- **Public** — Operations related to Public
- **Legacy** — Operations related to Legacy
- **Deprecated** — Operations related to Deprecated

## Why Jentic

- **Setup:** Wiring av_microservice_finance by hand means driving its lending operations one at a time against the hosted host: adding advances, recording repayments and charges, and swapping MSISDNs yourself. Through Jentic you install once, import av_microservice_finance from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** av_microservice_finance exposes flat operation paths rather than per-resource URLs, so limit the agent to the operations it needs, such as getBalanceEntity or getMsisdnList. You choose the operations it may call, so state-changing ones like addAdvance or churnSubscriber are not included unless you add them.
- **Credential handling:** Your av_microservice_finance credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register a subscriber advance' or 'get a subscriber balance', and Jentic returns the matching av_microservice_finance operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the av_microservice_finance use?

The av_microservice_finance uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I creates and registers a subscriber advance. with the av_microservice_finance?

Yes. Use the GET /addAdvance endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the av_microservice_finance?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I creates and registers a subscriber advance. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates and registers a subscriber advance.'. Jentic returns the matching av_microservice_finance operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the av_microservice_finance have?

The av_microservice_finance exposes 23 endpoints covering public, legacy, deprecated operations.

### Can I limit what my agent is allowed to do with the AV Microservice Finance API?

Yes. Because you run Jentic One yourself, your own rules decide which AV Microservice Finance operations and credentials the agent can use, and the API exposes flat operation paths so you scope it operation by operation. You can allow read-only calls such as getBalanceEntity and getMsisdnList while withholding state-changing ones like addAdvance, addRepayment, addCharge, and churnSubscriber. Those operations stay unavailable to the agent until you explicitly add them.