Israel Exchange Rates - ILS: API integration & OpenData services

Representative rate feed

Normalized JSON wrapper around the Bank of Israel PublicApi/GetExchangeRates endpoint. Each record carries currency_code, rate, change_pct, unit, and last_update. Used for: invoice revaluation in SAP/NetSuite, daily P&L marks, and FX gain/loss journals.

Multi-bank FX comparison

Side-by-side buy/sell/cash rates from the six Israeli banks covered by the app. Used for: retail best-rate routing, commercial hedging desk pricing intelligence, and travel platforms that want to surface "cheapest ILS at the airport" prompts.

Historical series API

Time-series endpoint returning arrays at daily granularity across configurable windows (1M, 3M, 6M, 1Y, or custom). Used for: analyst charts, VaR calculations, dissertation datasets, and fintech dashboards that need smoothed shekel benchmarks.

Converter micro-service

Drop-in REST service mirroring the in-app converter: POST /convert with amount, base, target, and optional rate-source. Supports the full 28-currency set plus derived crosses (EUR/USD via ILS). Used for: checkout pages, freelancer invoicing tools, and payroll conversion in olim-focused HR apps.

Widget-parity data push

Delivers the same payload the app's Android home-screen widget and Wear OS tile consume, shaped for push into internal mobile apps, Slack bots, or smart displays. Used for: treasury teams who need a glanceable shekel ticker without running the consumer app.

Alert & webhook layer

Threshold-based webhooks (e.g. USD/ILS crosses 3.80) with deduplication and retry. Used for: auto-hedge triggers, Telegram channel operators, and Olim finance groups who post "good rate" alerts to community members.

1. E-commerce checkout in shekels

Business context: An international Shopify merchant selling to Israeli customers wants accurate ILS pricing without over-charging. Data/API: Converter micro-service fed by the Bank of Israel representative rate plus a small spread. OpenData mapping: Public-feed read, no user consent required; falls outside the Financial Information Service Law 2021 scope, which keeps integration lightweight.

2. Olim salary-to-shekel payroll

Business context: HR platforms for new immigrants ("olim") need to convert foreign-currency salaries into ILS for tax reporting. Data/API: Historical series + last business-day representative rate. OpenData mapping: Pairs with PSD2-style account-information services to reconcile declared income against real deposits.

3. Treasury hedging alerts

Business context: A tech company booking USD revenue but paying Israeli salaries wants to hedge when USD/ILS crosses a target. Data/API: Alert/webhook layer wired to both the Bank of Israel feed and bank-level buy rates. OpenData mapping: Aligns with NextGenPSD2 (the working framework the Bank of Israel adapted) so downstream payment initiation can live on the same rails.

4. Travel comparison feature

Business context: A travel app promoting Tel Aviv trips wants to show "current ILS rate" and "best bank to buy shekels from today". Data/API: Multi-bank comparison endpoint, filtered to tourism-relevant currencies (USD, EUR, GBP). OpenData mapping: Purely read-only market data, keeps the travel app out of licensed financial-service territory.

5. Academic and policy research

Business context: Universities and think-tanks studying shekel volatility during geopolitical events need clean, cited datasets. Data/API: Historical series API with CSV export and source attribution ("Bank of Israel, retrieved via boi.org.il/PublicApi"). OpenData mapping: Straight OpenData usage with provenance metadata suitable for peer-reviewed publication.

Authentication & token refresh

POST /api/v1/ils-rates/auth/token
Content-Type: application/json

{
  "client_id": "your-tenant",
  "client_secret": "<redacted>",
  "scope": "rates.read bank_compare.read history.read"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "refresh_token": "rt_5f6..."
}

Representative rate query

GET /api/v1/ils-rates/boi/representative?date=2025-11-17
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "as_of": "2025-11-17T15:45:00+02:00",
  "source": "Bank of Israel PublicApi/GetExchangeRates",
  "base": "ILS",
  "rates": [
    {"code":"USD","unit":1,"rate":3.7241,"change_pct":-0.12},
    {"code":"EUR","unit":1,"rate":4.0518,"change_pct":+0.08},
    {"code":"JPY","unit":100,"rate":2.4062,"change_pct":-0.20},
    {"code":"AED","unit":1,"rate":1.0139,"change_pct":-0.11}
  ]
}

Six-bank comparison

GET /api/v1/ils-rates/banks/compare?pair=USD_ILS
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "pair": "USD/ILS",
  "as_of": "2025-11-17T15:50:00+02:00",
  "quotes": [
    {"bank":"Bank Hapoalim","buy":3.7402,"sell":3.7080,"cash_buy":3.76,"cash_sell":3.69},
    {"bank":"Bank Leumi","buy":3.7395,"sell":3.7085,"cash_buy":3.76,"cash_sell":3.69},
    {"bank":"Mizrahi Tefahot","buy":3.7410,"sell":3.7070},
    {"bank":"First International Bank (FIBI)","buy":3.7388,"sell":3.7092},
    {"bank":"Israel Discount Bank","buy":3.7401,"sell":3.7079},
    {"bank":"Israel Post","buy":3.7420,"sell":3.7060}
  ],
  "best_buy":"Israel Post",
  "best_sell":"Mizrahi Tefahot"
}

Webhook — threshold alert

POST https://your-domain.com/webhooks/ils-alert
X-Signature: t=1731852000,v1=...
Content-Type: application/json

{
  "event":"rate.threshold.crossed",
  "pair":"USD/ILS",
  "direction":"above",
  "threshold":3.80,
  "observed":3.8012,
  "source":"boi_representative",
  "observed_at":"2025-11-17T15:45:00+02:00"
}

# Retry policy: exponential backoff, 5 attempts, deduped via event_id.
# Error handling: 4xx = stop; 5xx = retry; timeout = retry.

Compliance & privacy

Israel's open finance environment is governed by the Financial Information Service Law 2021, the Regulation of Payment Services and Payment Initiation Law 2024 (effective June 2024), and the Bank of Israel's Proper Conduct of Banking Business Directive, which adapts NextGenPSD2 to the local market. Because Israel Exchange Rates - ILS consumes only published market data, our integrations stay inside the OpenData lane: no account-information services, no payment initiation, and no personal data flows. Where clients extend the stack into licensed territory (e.g. linking bank account balances), we add consent capture, audit logs, and data-minimization aligned with the Israel Privacy Protection Authority's 2024 guidelines. GDPR alignment is available for European clients serving Israeli residents.

Data flow / architecture

A typical pipeline: (1) Source — Bank of Israel PublicApi + per-bank HTML/JSON endpoints scraped under authorization → (2) Ingestion — scheduled workers (15-minute post-publication skew, plus intraday for bank rates) → (3) Normalization — ISO 4217 codes, common units, signed deltas → (4) Storage — time-series store (InfluxDB or Timescale) plus a "latest" hot cache → (5) Delivery — REST, GraphQL, or webhook subscriptions exposed to your backend.

About us

We are an independent studio focused on fintech and open-data API integration. Our engineers come from banking IT, payment gateways, and mobile protocol research, and we have shipped production APIs for FX, banking, and account-aggregation workloads across EMEA and APAC. For Israel specifically, we track the Bank of Israel's series database, the Licensing Law of 2024, and the NextGenPSD2 adaptation that the Banking Supervision Department has been rolling out.

• Protocol analysis of mobile apps (Android and iOS), including certificate pinning, signed requests, and encrypted payloads
• OpenFinance and OpenBanking integrations aligned with PSD2 / NextGenPSD2 and the Financial Information Service Law 2021
• SDKs in Python, Node.js, and Go with clean test harnesses
• End-to-end pipeline — scoping, reverse engineering, build, validation, compliance review
• Source code delivery from $300 — runnable API source code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted API and pay only per call, no upfront cost; ideal for teams that prefer usage-based pricing

Contact

Send us the target app (Israel Exchange Rates - ILS is already a good starting point) and your integration scenario — e.g. "USD/ILS hedging webhook" or "six-bank rate widget for a travel app" — and we will come back with a scope, timeline, and fixed quote.

Open the contact page

Engagement workflow

1. Scope confirmation — which rate sources (BOI only, banks only, or combined) and which delivery (REST / webhook / file dump).
2. Protocol analysis and API design — 2–5 business days for the ILS + six-bank combination.
3. Build and internal validation — 3–8 business days, including rate parity checks against the official Bank of Israel publication.
4. Documentation, samples, and test cases — 1–2 business days, delivered as OpenAPI plus Postman collection.
5. Typical first delivery: 5–15 business days. Compliance reviews or additional banks beyond the core six may extend timelines.

FAQ

Do you use the official Bank of Israel data?

Can you cover more than the six banks in the app?

How do you stay compliant?

Can the APIs feed a mobile app of ours directly?