Account API

Name: Account API API
Brand: Account API
Availability: InStock

★ Only Publicly Available SpecPaymentsPayment Processingnone4 EndpointsREST

For Agents

Programmatically get balance, get full account statement. Covers 4 operations.

Use for: I need to balance, I want to full account statement, Search for mini statement, Find all account enquiry

Quickstart

Get started with Account API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get balance"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Account API API.

Get Balance

Account Enquiry

Integrate Account API into automated workflows

Query and filter Account API records by parameters

Monitor Account API operational status and events

GET STARTED

Start building with Account API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Account API, keeping it validated and agent-ready.

The Equity Bank Account API allows a Merchant to fetch full/minimal transaction details for a given operative account, do Account Enquiries and Get a List of Accounts Opened. The API exposes 4 endpoints.

Use Cases

Patterns agents use Account API API for, with concrete tasks.

★ Payments Operations

Use the Account API to perform payments operations programmatically. The API provides 4 endpoints covering core functionality including get balance, get full account statement, get mini statement.

Call GET /accounts/balances/{countryCode}/{accountNumber} to get balance

Automated accounts Management

Automate accounts operations by combining multiple Account API endpoints. Agents can get full account statement and then get mini statement in a single workflow.

Call POST /accounts/fullstatement to get full account statement, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Account 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 none tokens manually.

Search Jentic for 'get balance', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — the equity bank account api allows a merchant to fetch full/minimal transaction details for a given operative account, do account enquiries and get a list of accounts opened.

METHOD

PATH

DESCRIPTION

GET

/accounts/balances/{countryCode}/{accountNumber}

Get Balance

POST

/accounts/fullstatement

Get Full Account Statement

GET

/accounts/ministatement/{countryCode}/{accountNumber}

Get Mini Statement

GET

/search/{countryCode}/{accountNumber}

Account Enquiry

GET

/accounts/balances/{countryCode}/{accountNumber}

Get Balance

POST

/accounts/fullstatement

Get Full Account Statement

GET

/accounts/ministatement/{countryCode}/{accountNumber}

Get Mini Statement

GET

/search/{countryCode}/{accountNumber}

Account Enquiry

Why though Jentic?

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

Credential isolation

Account API none 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., 'get balance') and Jentic returns the matching Account API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

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

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

Complementary

Paypal

Complementary payments API

Choose Paypal when you need a complementary approach to payments operations

FAQs

Specific to using Account API API through Jentic.

What authentication does the Account API use?

The Account API uses no authentication. 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 get balance with the Account API?

Yes. Use the GET /accounts/balances/{countryCode}/{accountNumber} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Account 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 get balance through Jentic?

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

How many endpoints does the Account API have?

The Account API exposes 4 endpoints covering accounts, search operations.