Bibit- Reksadana & Obligasi API integration services

Deliverables checklist

• API specification in OpenAPI / Swagger for every endpoint we ship
• Protocol & auth-flow report (OAuth-style token issuance, refresh, device binding, cookie/header chain)
• Runnable source code for login, portfolio, transaction and statement APIs in Python and Node.js (Go on request)
• Reksadana NAV history loader and SBN/obligasi order parser with field dictionaries
• Automated test suite, Postman collection, and integration documentation
• Compliance pack: consent text templates, data-retention guidance, OJK / UU PDP / KSEI alignment notes
• Optional hosted endpoints if you choose pay-per-call instead of source delivery

Two engagement models

1) Source code delivery from $300 — we hand over runnable API source code plus full documentation and tests; you pay after delivery once you are satisfied. Good when you want to host and own the integration yourself.

2) Pay-per-call hosted API — call our managed Bibit endpoints and pay only for the calls you make, with no upfront fee. Good for teams that want usage-based pricing and no infrastructure to run.

Both models include the same underlying protocol analysis and the same data coverage; the difference is only who hosts the runtime.

1 · Net-worth aggregation in a personal-finance app

Context: a budgeting or wealth app wants to show a user's full Indonesian investment picture next to their bank accounts.

Data / API: POST /v1/bibit/auth/login for a user-authorized session, then GET /v1/bibit/portfolio for reksadana units + NAV and GET /v1/bibit/sbn/orders for bond series. Optionally pull stock holdings from the Stockbit side.

OpenFinance mapping: behaves like an account-information service — read-only, consent-scoped, refreshable — consistent with the direction of OJK's open-API roadmap for wealth and the Bank Indonesia SNAP standard for payments.

2 · Accounting & reconciliation export

Context: a finance team or accountant needs every subscription, redemption and switch as ledger entries.

Data / API: GET /v1/bibit/transactions?from=&to=&type= returns normalized order rows with nav_used, units, amount, fee, status and settlement_date; a one-click format=xlsx produces a spreadsheet matching the in-app statement.

OpenFinance mapping: a statement / transaction export endpoint — the same primitive open-banking defines for bank accounts, applied to a wealth account.

3 · Tax-season SPT automation

Context: after Bibit added its Tax Report feature for the 2025 filing period, tax-prep tools want that data programmatically.

Data / API: GET /v1/bibit/tax-report?year=2025 aggregates realized gains, dividends and coupons per instrument and per tax year, mirroring the in-app report; results feed straight into an e-filing workflow.

OpenFinance mapping: a regulator-aligned data export — user-authorized, scoped to tax fields, logged for audit.

4 · Robo-advisor & suitability dashboard

Context: a fintech wants to compare a user's actual Bibit allocation to their stated risk profile.

Data / API: GET /v1/bibit/profile/risk returns the robo risk category and recommended allocation; combined with GET /v1/bibit/portfolio you can compute drift, Syariah-only filters, and rebalancing nudges.

OpenFinance mapping: personalization plus a compliance artifact — the risk record is documented evidence of suitability.

5 · Real-time webhook for portfolio & coupon events

Context: an analytics platform needs to react when an order settles, a coupon pays, or an auto-invest plan runs.

Data / API: register a callback; we POST { "event": "order.settled" | "coupon.paid" | "autoinvest.executed", "data": { ... } } with retry and HMAC signature, so your storage stays current without polling.

OpenFinance mapping: event-driven data sharing — the push side of an account-information service, useful for cash-flow forecasting and maturity ladders.

A · Account login & session

POST /v1/bibit/auth/login
Content-Type: application/json

{
  "phone": "+62812xxxxxxx",
  "otp": "<one-time-code>",
  "device_id": "<bound-device>"
}

200 OK
{
  "access_token": "<jwt>",
  "refresh_token": "<opaque>",
  "expires_in": 3600,
  "sid": "IDXxxxxxxxxx",          // KSEI Single Investor ID (masked)
  "kyc_status": "verified",
  "syariah_mode": false
}

# refresh
POST /v1/bibit/auth/refresh  { "refresh_token": "..." }

B · Portfolio & NAV snapshot

GET /v1/bibit/portfolio
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "as_of": "2026-05-11T08:00:00+07:00",
  "total_value_idr": 24750000,
  "holdings": [
    {
      "fund_id": "RD-XXXX",
      "name": "Sucorinvest Money Market Fund",
      "type": "money_market",
      "units": 18234.5512,
      "nav": 1356.21,
      "avg_cost": 1290.04,
      "market_value_idr": 24730000,
      "weight_pct": 99.9,
      "syariah": false
    }
  ],
  "goals": [ { "goal_id": "g1", "name": "Dana Darurat", "value_idr": 24730000 } ]
}

C · Transactions / statement export

GET /v1/bibit/transactions?from=2026-01-01&to=2026-03-31&type=all&format=json
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "count": 2,
  "items": [
    { "order_id":"o-1001","kind":"subscription","fund_id":"RD-XXXX",
      "amount_idr":1000000,"units":737.21,"nav_used":1356.21,
      "fee_idr":0,"status":"settled","placed_at":"2026-02-03T10:12:00+07:00",
      "settlement_date":"2026-02-05" },
    { "order_id":"o-1002","kind":"redemption","fund_id":"RD-YYYY",
      "amount_idr":500000,"units":-380.55,"nav_used":1313.88,
      "status":"processing","placed_at":"2026-03-28T14:40:00+07:00" }
  ]
}
# add &format=xlsx or &format=pdf for a downloadable statement

D · SBN/obligasi orders & webhook

GET /v1/bibit/sbn/orders
Authorization: Bearer <ACCESS_TOKEN>
=> [ { "series":"ORI026","nominal_idr":3000000,"coupon_pct":6.30,
       "coupon_freq":"monthly","next_coupon":"2026-06-15",
       "maturity":"2029-04-15","market":"primary","syariah":false } ]

# webhook delivered to your endpoint
POST https://your-app.example/webhooks/bibit
X-Signature: sha256=...
{
  "event": "coupon.paid",
  "data": { "series":"ORI026","amount_idr":15750,"paid_at":"2026-05-15" }
}

# error envelope (all endpoints)
{ "error": { "code":"rate_limited","message":"...","retry_after":30 } }

Regulatory alignment

Bibit operates under an APERD license and is registered and supervised by the OJK; investor accounts are anchored to KSEI's Single Investor Identification, and funds settle through licensed custodian banks — Bibit itself does not hold client money. Any integration we build respects that structure. We align with OJK consumer-protection and digital-financial-services rules, with the direction of the open-API roadmap (the OJK side for wealth/lending/insurance and Bank Indonesia's SNAP standard for payments), and with Indonesia's Personal Data Protection Law (UU PDP, Law No. 27 of 2022). Where data crosses borders we also keep GDPR-style minimization and purpose-limitation in mind for clients with EU exposure.

How we keep it clean

• Authorized access only — your consent or documented public/authorized APIs; never a bypass of security controls
• Consent text templates and per-user consent records stored with the data
• Data minimization — we drop or mask fields you do not need at ingestion
• Full request/response and access logging for audit
• Configurable retention windows and deletion endpoints
• NDAs and security review on request before any code is shared

About us

We are an independent technical studio focused on App interface integration and authorized API integration, with a strong fintech and OpenData track record. Our team has years of hands-on experience across mobile apps, payments, securities and cloud infrastructure, and we have shipped protocol-analysis and API projects for banking, brokerage, e-commerce, travel and media clients worldwide.

• Protocol analysis, interface refactoring, OpenData / OpenFinance integration, third-party interface integration
• Automated data scripting and delivery of interface documentation and test plans
• Custom Python / Node.js / Go SDKs, webhooks and ingestion pipelines
• Familiar with Indonesian wealth-tech, OJK / KSEI / Bank Indonesia expectations and multi-region privacy law
• Source code delivery from $300 — runnable API source code plus documentation; pay after delivery once satisfied
• Pay-per-call hosted API — use our endpoints and pay only per call, no upfront cost

Engagement workflow

1. Scope confirmation — which Bibit data and flows you need (login, portfolio, transactions, SBN, tax report, stocks).
2. Protocol analysis & API design — 2–5 business days depending on complexity.
3. Build & internal validation — 3–8 business days.
4. Documentation, samples & test cases — 1–2 business days.
5. First delivery typically in 5–15 business days; third-party or partner approvals may extend timelines.

Contact

To request a quote or start a Bibit- Reksadana & Obligasi integration, send us the target app (already known) and your concrete data needs — for example reksadana portfolio, transaction history, SBN/obligasi orders, NAV history, tax-report export, or a unified multi-app view.

Go to the contact page

FAQ

What do you need from me to start a Bibit integration?

How long does delivery take?

How do you handle compliance and OJK rules?

Can you also pull stock holdings, not just mutual funds and bonds?