Harbituach v2 · Admin

Overview

Activity

Transactions

Settings

cURL

Help

Waiting for status…

—

Minted at

—

Age

—

Last probe

—

Latency

—

Next heartbeat

—

Proactive refresh in

—

Force re-login in

—

Counters lifetime · this run shown per tile

—

Logins

— this run

—

Probes

— this run

—

Queries

— this run

—

Proxy bytes

— this run

Activity log

Newest 20 · View all →

No activity yet.

Recent queries

Newest 10 · View all →

Time	Person ID	Status	Latency	Proxy / Response	Files
No queries yet.

Run a query

Posts to /api/query

Person ID

Date of birth

ID issue date

Recent transactions

0

Time	Person ID	Status	Latency	Proxy / Response	Files
No queries yet.

API key

Required header: X-API-Key

Current key

Used by /api/query and /api/refresh. Stored in localStorage on this browser.

Har Bituach credentials

Username / ID

Password

Outlook (OTP source)

CloakBrowser reads OTP from this inbox

Email

Password

Residential proxy

WebShare sticky Israel

Proxy URL

Used for ALL Har Bituach traffic (login + probes + queries). Restart required.

Public cURL examples

Tap any box to copy

Status (no auth)

Query — Chen Shlush (test ID)

Force re-login

Activity log

Newest first · last 200 events · persisted across restarts

No activity yet.

How this works

Probe + re-login policy

The service keeps a Har Bituach session alive between logins by sending a small heartbeat ping. If the ping shows the session is dead, OR if it's been too long since the last login, it logs in again automatically.

1 · Heartbeat probe interval

How often we ping /sso/Auth/MoreInsurance to check + refresh the session.

—

2 · Skip probe if recent traffic

If a real /api/query ran within this window, we skip the next probe — the query already touched the session.

—

3 · Re-login trigger A — probe says DEAD

If the probe response shows we got bounced to login (redirect to login.gov.il, oauth2, or harb's error page), we re-login. Requires — consecutive DEAD probes (prevents flapping on transient redirects).

—

4 · Re-login trigger B — probe UNKNOWN

If the probe keeps failing with weird responses (5xx, network errors, proxy hiccups), we re-login as a recovery. Requires — consecutive UNKNOWN probes.

—

5 · Re-login trigger C — hard age ceiling

Even if probes are happy, force a re-login this often. Catches cases where the server says "alive" but the session is actually broken in subtle ways.

—

6 · Re-login backoff

After a failed login, wait this long before trying again. Prevents login storms when something is broken upstream.

5m