Install Jentic One Beta

Connect the BCA Developer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BCA Developer 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbca.co.id%2Fbca" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbca.co.id%2Fbca" | 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 BCA Developer API.

Issue an OAuth access token via POST /api/oauth/token or the B2B variant POST /openapi/v1.0/access-token/b2b

Inquire a business debit card via POST /openapi/bdc/v1.0/inquiry-card and update its status

Set or change a business debit card spending limit via POST /openapi/bdc/v1.0/setting-limit

Run a corporate balance inquiry with POST /openapi/v1.0/balance-inquiry

GET STARTED

Start building with BCA Developer API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BCA Developer API for, with concrete tasks.

★ Corporate Cash-Position Reporting

A treasury team needs to pull end-of-day balances and statements across multiple BCA corporate accounts. The API exposes POST /openapi/v1.0/balance-inquiry for live balances and POST /openapi/v1.0/bank-statement for itemised transactions. Combine with the OAuth B2B token endpoint and the run becomes a scheduled job hitting BCA each morning to refresh the cash dashboard.

Issue a B2B token via POST /openapi/v1.0/access-token/b2b, then call POST /openapi/v1.0/balance-inquiry and POST /openapi/v1.0/bank-statement for each account

Business Debit Card Lifecycle

Finance ops teams managing corporate cards can use POST /openapi/bdc/v1.0/inquiry-card to look up card status, POST /openapi/bdc/v1.0/setting-limit to adjust spend caps, and POST /openapi/bdc/v1.0/update-status to block or unblock a card after travel or termination events. The flow sits behind an internal admin tool or a Slack-driven approval bot.

Call POST /openapi/bdc/v1.0/inquiry-card to confirm the card, then POST /openapi/bdc/v1.0/setting-limit to raise the daily limit for a travelling employee

Virtual Account Reconciliation

Marketplaces and billers using BCA virtual accounts need to confirm whether incoming transfers have settled. POST /openapi/v1.0/transfer-va/inquiry returns the transfer record and POST /openapi/v1.0/transfer-va/status returns its current state. The reconciliation job uses both to mark customer invoices paid as soon as funds clear.

Call POST /openapi/v1.0/transfer-va/inquiry for each pending invoice, then POST /openapi/v1.0/transfer-va/status to confirm settlement before marking paid

Agent-Driven Treasury Lookup via Jentic

A finance ops chat agent can use the BCA Developer API through Jentic to answer ad-hoc treasury questions like 'what's the balance on the operating account right now?' without operators handling OAuth refresh. Jentic isolates the BCA client credentials in its vault and exposes the 12 BCA operations as discoverable tools indexed by natural-language intent.

Search Jentic for 'bca account balance inquiry', load the POST /openapi/v1.0/balance-inquiry schema, and execute against the requested account

Key Endpoints

12 endpoints — bank central asia's developer api exposes core retail and corporate banking operations to authorised partners.

METHOD

PATH

DESCRIPTION

POST

/api/oauth/token

Issue an OAuth access token

POST

/openapi/v1.0/access-token/b2b

Issue a B2B OAuth access token

POST

/openapi/v1.0/balance-inquiry

Inquire on a corporate account balance

POST

/openapi/v1.0/bank-statement

Retrieve a corporate bank statement

POST

/openapi/bdc/v1.0/inquiry-card

Inquire on a business debit card

POST

/openapi/bdc/v1.0/setting-limit

Set a business debit card spending limit

POST

/openapi/v1.0/transfer-va/inquiry

Inquire on a virtual account transfer

POST

/openapi/v1.0/transfer-va/status

Check the status of a virtual account transfer

POST

/api/oauth/token

Issue an OAuth access token

POST

/openapi/v1.0/access-token/b2b

Issue a B2B OAuth access token

POST

/openapi/v1.0/balance-inquiry

Inquire on a corporate account balance

POST

/openapi/v1.0/bank-statement

Retrieve a corporate bank statement

POST

/openapi/bdc/v1.0/inquiry-card

Inquire on a business debit card

POST

/openapi/bdc/v1.0/setting-limit

Set a business debit card spending limit

POST

/openapi/v1.0/transfer-va/inquiry

Inquire on a virtual account transfer

POST

/openapi/v1.0/transfer-va/status

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the BCA Developer API by hand means running the OAuth and B2B access-token exchanges, choosing between the sandbox and production hosts, and signing each banking request yourself. Through Jentic you install once, import the BCA Developer API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

BCA carries its account and virtual-account targets in the request body rather than as a resource in the URL path, so scope the agent to the operations it needs, such as balance inquiry or bank statement retrieval. You choose that operation set, so business debit card limit setting is not included unless you add it.

Credential isolation

Your BCA OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'BCA account balance inquiry' or 'check a virtual account transfer status', and Jentic returns the matching BCA operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using BCA Developer API through Jentic.

What authentication does the BCA Developer API use?

BCA uses bearer tokens issued via OAuth. POST /api/oauth/token issues a partner token and POST /openapi/v1.0/access-token/b2b issues a B2B token. Pass the token as Authorization: Bearer <token> on all subsequent calls. Through Jentic the client credentials live in the vault and only a scoped token reaches the agent.

Can I fetch a corporate account balance with the BCA API?

Yes. POST /openapi/v1.0/balance-inquiry returns the live balance for a corporate account. Pair it with POST /openapi/v1.0/bank-statement to also retrieve recent transactions in the same run.

How do I check a virtual account transfer status through Jentic?

Search Jentic for 'check bca virtual account transfer status', which surfaces POST /openapi/v1.0/transfer-va/status. Load the schema, supply the transfer reference, and execute to receive the current settlement state.

What are the rate limits for the BCA Developer API?

The OpenAPI spec does not declare explicit rate limits. BCA applies per-partner quotas declared in the partner agreement and may throttle aggressive polling. Use the sandbox host for development and respect any 429 responses in production.

Does the BCA API expose business debit card management?

Yes. POST /openapi/bdc/v1.0/inquiry-card looks up a card, POST /openapi/bdc/v1.0/setting-limit adjusts its daily spend cap, and POST /openapi/bdc/v1.0/update-status changes the card's active/blocked state. All require a partner-scoped OAuth token.

Is there a sandbox for testing the BCA API?

Yes. The OpenAPI spec declares both https://sandbox.bca.co.id (sandbox) and https://api.bca.co.id (production) as servers. Develop against the sandbox host, and switch the base URL when promoting to live banking traffic.

Can I limit what my agent is allowed to do with the BCA Developer API?

Yes. Because you run Jentic One yourself, your own rules decide which BCA operations and credentials the agent can use, so you can grant only what a task needs, such as POST /openapi/v1.0/balance-inquiry and POST /openapi/v1.0/bank-statement for read-only cash reporting. Since BCA carries the account and virtual-account targets in the request body rather than in the URL path, you scope by operation rather than by resource, and you leave state-changing calls like POST /openapi/bdc/v1.0/setting-limit out of the set unless you deliberately add them. The stored OAuth client credentials are injected only for the operations you have allowed, so the agent cannot reach BCA endpoints you did not include.

BCA Developer API

Name: BCA Developer API
Brand: BCA Developer API
Availability: InStock

Official vendor OpenAPI document · agent-readyFinanceBankingbearer12 EndpointsREST

For Agents

Issue BCA OAuth tokens, inquire balances and bank statements, manage business debit card limits, and check virtual-account transfer status. Useful for fintech back-office and treasury agents.

Use for: I need to fetch a corporate account balance from BCA, Pull last month's bank statement for an account, Inquire on a business debit card, Update the spending limit on a corporate card

Not supported: Does not handle retail consumer banking, FX trading, or lending - use for partner-scoped corporate balance, statement, virtual-account, and business debit card operations only.

Bank Central Asia's developer API exposes core retail and corporate banking operations to authorised partners. The API covers OAuth 2.0 access-token issuance (including a B2B variant), business debit card inquiry and limit management, balance and statement retrieval, virtual account transfer inquiry and status, and a marketplace account-opening flow. Sandbox and production endpoints are both declared, so integrators can develop against the sandbox before promoting to live banking traffic.

Jentic One on Github View OpenAPI Document

Connect the BCA Developer API to your agent

Capabilities

Start building with BCA Developer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

BCA Developer API