BCA Developer API

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

✓ Official Vendor SpecFinanceBankingbearer12 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.

Quickstart

Get started with BCA Developer 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:
"bca account balance inquiry"

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

Capabilities

What an agent can do with BCA Developer API 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 API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use BCA Developer API 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

Why though Jentic?

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

Credential isolation

BCA OAuth client_id and secret are stored encrypted in the Jentic vault. The vault performs the access-token exchange and exposes only a short-lived scoped bearer token to the agent — raw banking credentials never enter the agent's context when calling endpoints like POST /openapi/v1.0/balance-inquiry.

Intent-based discovery

Agents search by intent (e.g. 'bca account balance inquiry' or 'check bca virtual account transfer status') and Jentic returns matching BCA operations with their input schemas across the 12 available endpoints.

Time to first call

Direct BCA integration: 1-2 weeks given partner onboarding, OAuth setup, and sandbox-to-production promotion. Through Jentic: hours rather than weeks once partner credentials are stored in the vault — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Basesnap API

Database snapshot service — back up the ledger database that ingests BCA statement and balance data

Use Basesnap for state database backups; use BCA for live banking data.

Complementary

Bbot API

Restaurant ordering platform — pair with BCA when reconciling Indonesian merchant payouts

Use Bbot for the order side and BCA for the bank-side reconciliation.

Alternative

Baseten API

Unrelated ML platform; listed as a placeholder peer in the absence of a competing Indonesian banking API in the corpus

Not a real alternative — included only because the corpus does not contain a competing Indonesian bank API.

FAQs

Specific to using BCA Developer API 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.