Tigo TigoPesa API

Name: TigoPesa API
Brand: TigoPesa API
Availability: InStock

✓ Official Vendor SpecPaymentsBilling Subscriptionsbearer8 EndpointsREST

For Agents

Programmatically generate access token, system health check. Covers 8 operations with bearer authentication.

Use for: I need to generate access token, I want to system health check, Search for authorize a payment, Find all validate mfs account

Install Jentic One Beta

Connect the TigoPesa API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TigoPesa API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 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 | sh

Step 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 instance

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

Capabilities

What an agent can do with TigoPesa API.

Generate access token

System health check

Authorize a payment

Validate MFS account

GET STARTED

Start building with TigoPesa API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use TigoPesa API for, with concrete tasks.

★ Payments Operations

Use the TigoPesa API to perform payments operations programmatically. The API provides 8 endpoints covering core functionality including generate access token, system health check, authorize a payment.

Call POST /v1/oauth/generate/accesstoken to generate access token

Automated Authentication Management

Automate authentication operations by combining multiple TigoPesa API endpoints. Agents can system health check and then authorize a payment in a single workflow.

Call GET /v1/tigo/systemstatus to system health check, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TigoPesa API 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 bearer tokens manually.

Search Jentic for 'generate access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — tigopesa mobile money api for payment authorization, mfs account validation, remittance deposits, and transaction management.

METHOD

PATH

DESCRIPTION

POST

/v1/oauth/generate/accesstoken

Generate access token

GET

/v1/tigo/systemstatus

System health check

POST

/v1/tigo/payment-auth/autorize

Authorize a payment

POST

/v1/tigo/mfs/validateMFSAccount

Validate MFS account

POST

/v1/tigo/mfs/depositRemittance

Deposit remittance

POST

/v1/tigo/mfs/reverseTransaction

Reverse a transaction

GET

/v1/payment-auth/transactions/{MasterMerchantId}{transactionRefId}

Get payment auth transaction status

GET

/v1/tigo/mfs/depositRemittance/transactions/{PaymentAggregatorId}{transactionRefId}

Get remittance transaction status

POST

/v1/oauth/generate/accesstoken

Generate access token

GET

/v1/tigo/systemstatus

System health check

POST

/v1/tigo/payment-auth/autorize

Authorize a payment

POST

/v1/tigo/mfs/validateMFSAccount

Validate MFS account

POST

/v1/tigo/mfs/depositRemittance

Deposit remittance

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

TigoPesa API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'generate access token') and Jentic returns the matching TigoPesa API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct TigoPesa API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using TigoPesa API through Jentic.

What authentication does the TigoPesa API use?

The TigoPesa API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I generate access token with the TigoPesa API?

Yes. Use the POST /v1/oauth/generate/accesstoken endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the TigoPesa API?

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 generate access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'generate access token'. Jentic returns the matching TigoPesa API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the TigoPesa API have?

The TigoPesa API exposes 8 endpoints covering authentication, mfs, payments operations.

Tigo TigoPesa API

Connect the TigoPesa API to your agent

Capabilities

Start building with TigoPesa API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs