Skip to content

Bank Hapoalim
CompanyTypes Hapoalim
Engine Browser (Pipeline)
Credentials userCode, password (plus otpCodeRetriever callback in options)
OTP Conditional — only on unrecognised devices
Phase chain INIT → HOME → LOGIN → (OTP-FILL conditional) → BIND-API-MEDIATOR → API-DIRECT-SCRAPE → TERMINATE
Source Banks/Hapoalim/HapoalimPipeline.ts

Quick example

const scraper = createScraper({
  companyId: CompanyTypes.Hapoalim,
  startDate: new Date('2024-01-01'),
  otpCodeRetriever: async phoneHint => await myInbox.getSmsCode(phoneHint),
});

const result = await scraper.scrape({
  userCode: '1234567',
  password: 'mypassword',
});

Known quirks

  • Hapoalim uses OTP-FILL only, never OTP-TRIGGER — the bank auto-sends the code when it decides a device is unrecognised.
  • On remembered devices, the OTP form simply doesn't appear and the otpCodeRetriever is never invoked.
  • Balance is single-bank-account (balanceKind: ACCOUNT) — the bank exposes a single bankAccountUniqueId per customer, resolved by the hard-model balance step.

Hard-model post-auth

After login, Hapoalim uses the hard-model post-auth path (withBrowserApiDirect): instead of the generic AUTH-DISCOVERY / ACCOUNT-RESOLVE / DASHBOARD / SCRAPE / BALANCE-RESOLVE chain, the HAPOALIM_SHAPE IApiDirectScrapeShape (Banks/Hapoalim/scrape/HapoalimShape.ts) declares the exact accounts, balance, and transactions API calls, issued directly through the live login page. See api-direct-scrape for the phase contract.