Co APIclalbit.co.il ↗
Check if any Israeli-registered vehicle has active Clal Insurance coverage on a given date. Returns coverage status, Hebrew summary, and full response data.
What is the Co API?
The Clal Bit API exposes 1 endpoint — check_vehicle_insurance_status — that returns 6 structured fields telling you whether a specific vehicle holds an active Clal Insurance policy on a given date. Submit a license plate number and a date in DD/MM/YYYY format and get back a boolean coverage flag, a Hebrew-language result summary, and the full upstream response object, all in a single call.
curl -X GET 'https://api.parse.bot/scraper/34162a50-b738-4910-8137-f7052ab657f8/check_vehicle_insurance_status?event_date=10%2F07%2F2026&license_number=1234567' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace clalbit-co-il-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.clal_insurance_verification_api import ClalInsurance, InsuranceStatus
client = ClalInsurance()
# Check vehicle insurance coverage for a specific date
status = client.insurancestatuses.check(license_number="1234567", event_date="10/06/2026")
print(status.has_coverage, status.message)
print(status.license_number, status.event_date)
Check whether a vehicle has a valid Clal Insurance policy on a specific date. Returns a boolean coverage indicator and a Hebrew-language message summarizing the result. The upstream API is queried in real time; a vehicle with no Clal policy returns has_coverage=false (not an error). License numbers are 5-8 digit Israeli vehicle registration numbers; event_date is any calendar date in DD/MM/YYYY format.
| Param | Type | Description |
|---|---|---|
| event_daterequired | string | Date to check coverage for, in DD/MM/YYYY format. |
| license_numberrequired | string | Vehicle registration number (5-8 digits). |
{
"type": "object",
"fields": {
"message": "string, Hebrew-language summary of the result",
"event_date": "string, the queried date in DD/MM/YYYY format",
"is_success": "boolean indicating the API query completed successfully",
"has_coverage": "boolean indicating whether the vehicle has active insurance on the given date",
"raw_response": "object containing the full upstream API response fields",
"license_number": "string, the queried vehicle registration number"
},
"sample": {
"data": {
"message": "בתאריך 10/06/2026 נמצא ביטוח תקף לרכב שמספרו 1234567 בחברת כלל ביטוח.",
"event_date": "10/06/2026",
"is_success": true,
"has_coverage": true,
"raw_response": {
"HasKisui": true,
"IsSuccess": true,
"ErrorMessage": null,
"FullErrorMsg": null,
"IsGeneralError": false,
"ResponseErrorMessageInClient": null,
"ResponseIsAppErrorIsAppError": false,
"ResponseShowErrorMessageInClient": false,
"ResponseIsAppErrorAppErrorMessage": null
},
"license_number": "1234567"
},
"status": "success"
}
}About the Co API
What the API Returns
The check_vehicle_insurance_status endpoint accepts two required inputs: license_number (the vehicle registration number, 5–8 digits) and event_date (the date of interest, formatted as DD/MM/YYYY). The response includes has_coverage, a boolean that directly answers whether the vehicle held an active Clal Insurance policy on that date, and is_success, which confirms the query itself completed without error.
Response Fields
Alongside the boolean flags, the response echoes back license_number and event_date so results can be matched to the original query without extra bookkeeping. The message field contains a Hebrew-language narrative summary of the result — useful for displaying directly to Israeli-market end users without translation overhead. The raw_response object contains the full set of fields returned from the source, giving you access to any additional structured data beyond what the normalized fields expose.
Data Scope and Coverage
This API is specific to Clal Insurance (כלל ביטוח), one of Israel's major insurers. It does not aggregate coverage across other Israeli insurance providers. The endpoint is suited for point-in-time lookups — checking coverage on a particular historical or future date — rather than returning a policy timeline or history. Input validation is handled on the API side; license numbers outside the 5–8 digit range will not return valid coverage data.
The Co API is a managed, monitored endpoint for clalbit.co.il — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when clalbit.co.il changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official clalbit.co.il API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Verify insurance coverage at the time of a road accident using
event_dateandlicense_number - Automate pre-rental vehicle insurance checks before handing over car keys
- Integrate into fleet management dashboards to flag vehicles with lapsed Clal coverage
- Display Hebrew-language coverage confirmations directly in Israeli consumer-facing apps using the
messagefield - Audit historical coverage status for a specific date using a past
event_datevalue - Build insurance compliance checks into parking or toll management platforms
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Clal Insurance provide an official public developer API for coverage lookups?+
What does `has_coverage` actually tell me, and how is it different from `is_success`?+
is_success is true when the API query completed and received a valid response — it does not say anything about coverage itself. has_coverage is the substantive answer: true means the vehicle had an active Clal Insurance policy on the queried date, false means it did not. A query can succeed (is_success: true) while returning no coverage (has_coverage: false).Can I check coverage for insurers other than Clal — such as Harel, Migdal, or Menorah?+
Does the API return a full policy history or coverage period, or just a single date check?+
event_date supplied — it does not return policy start/end dates, coverage periods, or a history of past policies. You can fork it on Parse and revise it to add a timeline or batch-date endpoint if your use case requires that.What license number formats are accepted?+
license_number parameter accepts Israeli vehicle registration numbers between 5 and 8 digits. Numbers outside that range will not produce valid coverage results. The event_date must be in DD/MM/YYYY format; other date formats are not supported.